Repository navigation
Guide §6.0: the gate skips a row only on its own written condition; a skip resolves only that row - #59
Merged
Conversation
…y when" condition; a skip resolves only that row Changes what "resolved" means instead of adding guards: a row is resolved when answered or skipped by its own condition; nothing else resolves a row. The existing every-row-resolved loop, step-5 check and §12.11 therefore also block skipping by judgment and stopping after a skip. - Gate step 3: the one skip, a one-line note, "a skip resolves that row only", re-check conditions when an earlier answer changes. Steps 4, 5: "resolved"; new checklist mark `not applicable (…; <row> = <answer>)`, invalid if the quoted condition is not false. - §6.0 bullet, §5.5, row order, §0 comment, §12.11, §14 rewritten in place. - Removed: §7 "Rows that stop mattering" column, its checker check (MOOT), §14 and audit (k) halves — the conditions carry moot rows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eeps its number; re-pin 'Written against' to base da81a7d (quoted passages unchanged, verified with grep -F) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…teria of the rows it makes moot (a skipped row has no line of its own) Fixes a regression from da81a7d: "Rows an option makes moot are not listed here" was read as "do not list their tests" (K3: the no-grader line kept the learning-loop tests in force). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uoted passages unchanged, verified with grep -F) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 19, 2026
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
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.
Part 5 (issue #48, "rows that stop mattering"): the gate skips a row only when its own written "Applies only when" condition is false.
Approach
Instead of adding guards, this changes what "resolved" means. A row is resolved when it is answered, or skipped by its own written condition. Nothing else resolves a row. The existing every-row-resolved loop (step 4), the step-5 "unresolved → go back" check, and §12.11 therefore also block skipping by judgment and stopping after a skip.
What changes
not applicable (applies only when <row> is <id>; <row> = <answer>), which is invalid if the quoted condition is not false.Tested (Opus 5.5)
Each probe's expected asked and skipped rows were computed from the spec, and a script compared them with the transcript (
experiments/gate-skip/check_probe.py, local).da81a7d)da81a7d)18c4fbd18c4fbd)Not in this PR
When an option removes a model role, its table line doesn't say what happens to that role's "setting required" test. Seen 3 times; logged on #48.
🤖 Generated with Claude Code