Skip to content

docs: a verification that checked the adjacent thing (#2492) - #2505

Merged
gHashTag merged 1 commit into
masterfrom
docs/adjacent-verification
Aug 23, 2026
Merged

gHashTag merged 1 commit into
masterfrom
docs/adjacent-verification

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

A gate written yesterday for a question nobody was asking went red on real data today. What it found was eleven blog posts absent from a live site for two days.

A deploy had replaced the site's application bundle with one built from a different repository. Eleven posts existed only in the old bundle — never migrated into the shared source — so the swap removed them. They had no static pages either, so nothing served them at all.

That deploy was verified before pushing. Its commit message says so:

Verified before pushing: deck/, .claude/, blog/ (29) and ru/ (11) untouched

Every word of that is true, and it is the wrong question. It checked the static trees; the loss was entirely inside the bundle. A verification aimed one step to the left of the thing being changed is harder to notice than no verification at all, because the commit reads as checked.

The rule: name what your change REPLACES, and verify that.

And a gate is not tested until it is red on data you did not plant. Four planted control cases all passed before the gate had ever seen a real deploy. Replaying it over 160 commits of history found three drops — two healed by the next deploy, one not. That replay is now a mode of the tool rather than a script run once, and it has its own three planted cases: an unhealed drop reds, a healed drop stays green and says why, a clean history does not invent one.

All eleven posts are restored and live in both languages, verified by content on production rather than by exit code.

Refs #2492

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 06:13:46 UTC

Summary

Status Count
Total Open PRs 6
PRs with Failing Checks 2
PRs with All Checks Green 4
READY 3
FAILING 2
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag merged commit 0191875 into master Aug 23, 2026
19 of 21 checks passed
@gHashTag
gHashTag deleted the docs/adjacent-verification branch August 23, 2026 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant