docs(register): /review-rr strategic — curate, and name the fails-green cluster - #419
Merged
Merged
Conversation
C-324 RESOLVED AS STALE. It described a live credential sitting in a
server log. The token was revoked 2026-08-01 (GDL allows one per
account, so issuing the replacement forced it), the leaking harvester
was superseded when the server moved to v1.11.0, and the log itself no
longer exists — destroyed by C-339. Every remediation the entry
prescribed had happened. The register had gone stale in exactly the way
it keeps warning about, and a reader would have acted on exposure that
ended three days earlier.
"FAILS GREEN" CLUSTER NAMED — eight open entries (C-317, C-331, C-336,
C-337, C-338, C-339, C-340, C-341) that are symptoms of one root cause:
mechanisms that report success while not doing the thing. Individually
small; together they say this project's characteristic failure is
silence, not error. The cluster carries a design rule rather than eight
separate fixes — absence of an error is not evidence of success, so any
new mechanism needs an answer to "how would I know if this silently did
nothing?" before it ships.
FIVE TRIGGERS REWRITTEN. C-332 was perpetual ("any change to these
files") and now names the act that creates the exposure. C-339 stated a
rule where a trigger belongs. C-70, C-72, C-333 were vague or
passive-wait.
FIVE DEMOTED to tech-debt backlog on the C-136 precedent: C-46, C-116,
C-117, C-147, C-155 — mechanical, single-file, never fired, loud rather
than silent if they ever do. C-70 and C-72 were on the demotion list and
were KEPT: their triggers had just been made concrete, and demoting an
entry immediately after making it actionable is incoherent.
Blind spots reported, not registered (skill rule): bus factor — one
person holds every credential, all server access, and the operational
knowledge, unnamed across 341 entries; upstream source discontinuation;
whether a past release's grid can still be rebuilt.
Counts: 45 -> 39 open, Tier 3 12->11, Tier 4 25->20, struck 110->115.
METHOD NOTE, kept because it is evidence rather than an anecdote. The
cluster table first used `| C-317 |` as its leading column, which
collides with the summary-row format, and the repair used
`replace(..., 1)` — which hit the FIRST match and silently bolded eight
real summary rows. Two edits, both plausible, both wrong, neither
raising an error. The guards caught it. Writing the fails-green cluster
produced two instances of failing green.
Verified: full suite exit 0, validate_docs.sh exit 0, all register and
changelog guards green, 39 open rows == header 39.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/review-rr strategic, then curation. Verdict was NEEDS CURATION — fundamentally sound, but one stale entry, six weak triggers, five inert entries, and the dominant cluster unnamed.C-324 resolved as stale
It described a live credential in a server log. Reality:
logs/refresh.log"The register had gone stale in the way it keeps warning about. A reader would have acted on exposure that ended three days earlier.
The "fails green" cluster, named
Eight entries — C-317, C-331, C-336, C-337, C-338, C-339, C-340, C-341 — that are symptoms of one root cause: mechanisms that report success while not doing the thing.
Individually small. Together they say this project's characteristic failure is silence, not error. The cluster carries a design rule rather than eight fixes: absence of an error is not evidence of success, so any new mechanism needs an answer to "how would I know if this silently did nothing?" before it ships.
Also
45 → 39 open · Tier 3 12→11 · Tier 4 25→20
Method note
The cluster table first used
| C-317 |as its leading column, which collides with the summary-row format; the repair usedreplace(..., 1), which hit the first match and silently bolded eight real summary rows. Two edits, both plausible, both wrong, neither raising an error. The guards caught it.Writing the fails-green cluster produced two instances of failing green. Kept in the changelog as evidence.
Verification
Full suite exit 0 ·
validate_docs.shexit 0 · all register + changelog guards green · 39 open rows == header 39