CLAUDE.md: 5+3 sequencing + base case — "before any claim" was unbounded - #233
Merged
Conversation
…bounded "Run [the 5+3 pattern] before any claim enters the canon" read literally requires a council on the council's own ratified verdict — which is itself a claim entering the canon — and so on without bottom. An unconditional per-claim obligation whose discharge is itself a claim diverges unless the base case is explicit. Stated: one pass (savants -> consolidate -> reviewers on the consolidated draft ONLY -> ratified result lands) discharges the obligation; the verdict enters without a second council. This matches how the pattern has always actually run — the lance-graph 5plus3 skill already sequences it exactly this way — so this is wording, not a behaviour change. Provenance: the lance-graph recursion sweep (E-THE-HYGIENE-RULE-RECURSED-1), which found the same missing-base-case shape in its own board-hygiene rule (#884 -> #885 chain) and derived the two-question test this applies: (1) discharge creates a new artifact of the governed kind -> divergent; (2) unconditional trigger -> divergent. The 5+3 wording hit both. Append-only respected: nothing deleted; the amendment is added at the rule and cites its pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
The prior commit's base case ("one pass, no second council") was
under-specified on two counts, corrected per operator ruling:
1. The ORDER is the load-bearing part: the 5 savants first streamline the
open points into a hardened draft; the 3 reviewers attack ONLY the
already-hardened draft; findings are fixed. Never the 3 in parallel with
or ahead of the 5 — raw session output is typically not yet hardened,
and attacking unhardened material invites hallucinated, deflected,
reactive coding. The reviewers need a consolidated object to break,
not a moving one.
2. The termination is NOT "once ever": a further full 5+3 pass on the
result is permitted as a deliberate re-invocation when warranted. What
bounds the recursion is that re-running is a choice, not an automatic
per-claim obligation — the divergence in the old wording came from the
obligation being unconditional, not from re-runs existing.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
AdaWorldAPI
marked this pull request as ready for review
August 4, 2026 13:57
AdaWorldAPI
changed the title
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
2 participants
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.
One file, one amendment, doc prose only. No code, no mechanism change — the amendment states how the pattern is ruled to run.
The defect
CLAUDE.md doc-family item 9: "Run [the 5+3 hardening pattern] before any claim enters the canon."
Read literally, this diverges: the council's ratified verdict is itself a claim entering the canon, so it requires a council, whose verdict requires a council, without bottom. An unconditional per-claim obligation whose discharge is itself a claim has no base case unless one is stated.
The amendment (operator-ruled sequencing, 2026-08-04)
The order is the load-bearing part:
The base case follows from 4: each cycle terminates (streamline → attack → fix → land), and a further full pass is a deliberate re-invocation when warranted — never an automatic per-claim obligation. That choice-vs-obligation distinction is what bounds the recursion; the old wording's divergence came from the obligation being unconditional, not from re-runs existing.
Provenance
Found by the lance-graph recursion sweep (
E-THE-HYGIENE-RULE-RECURSED-1), whose two-question test fires on both counts here: (1) discharge creates a new artifact of the governed kind — the verdict is a canon claim; (2) the trigger is unconditional — "any claim". Mirror on the consumer side: lance-graph.claude/agents/5plus3-council.md§ "Sequencing invariant + base case" (same ruling, landed in lance-graph #886).Append-only respected: nothing deleted or regraded; the amendment is added at the rule and cites its pass.
Test plan
Prose only — nothing to regress.
🤖 Generated with Claude Code
https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki