docs(skills): fix iter-134's own Gate-4 control — a known-absent literal poisons itself in a self-describing file - #571
Merged
Conversation
…ral poisons itself in a self-describing file Same iteration, same edit, corrected by running it. Iteration 134's Gate-5 edit told Gate 4 to pair the charter cheap tell with two controls: a known-present `ITERATION <N-2>` and a known-absent `ITERATION 999`. Verifying the landed record, the known-absent control returned **1**, not 0. Cause: the STATUS stamp iteration 134 had just written *documents the control*, so the string `ITERATION 999` is now in the charter permanently. The charter is a file the loop writes about itself, so any literal named as "known-absent" stops being absent the moment a record mentions it — and unlike the case bug it was added to fix, this one degrades silently in the safe-looking direction: the control reads as firing while proving nothing. Fix: keep the known-PRESENT control, which is the one that actually detects the failure mode (a broken instrument reads 0 on a healthy charter). Drop the known-absent literal, and where a structural second check is wanted, assert the rotation invariant `grep -c "^## STATUS 2026" == 3`, which is anchored to line-start and cannot be tripped by prose. Saved in the MAIN checkout first (same inode via the ~/.claude symlink, so it is live for both missions now) and mirrored here so origin matches — no drift. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sunholo-voight-kampff
enabled auto-merge (squash)
August 3, 2026 13:26
|
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.
Correction to the Gate-5 skill edit landed minutes ago in #570 — caught by running the check it added.
#570 told Gate 4 to pair the charter cheap tell with two controls: known-present
ITERATION <N-2>and known-absentITERATION 999. Verifying the landed record, the known-absent control returned1, not0.Cause: the STATUS stamp #570 had just written documents the control, so
ITERATION 999is now in the charter permanently. The charter is a file the loop writes about itself, so any literal named "known-absent" stops being absent the moment a record mentions it. And unlike the case-sensitivity bug it was added to fix, this one fails silently in the safe-looking direction — the control reads as firing while proving nothing.Fix: keep the known-present control (the one that actually detects the failure mode: a broken instrument reads
0on a healthy charter). Drop the known-absent literal. Where a structural second check is wanted, assert the rotation invariantgrep -c "^## STATUS 2026" == 3— anchored to line-start, untrippable by prose.Saved in the main checkout first (same inode via the
~/.claudesymlink, so it is live now) and mirrored here — no drift.🤖 Generated with Claude Code