process: the orchestrator holds the review bound, the packet is finished before the verdict, progress is evidence - #22
Open
paveq wants to merge 1 commit into
Conversation
…hed before the verdict, progress is evidence, and a report names what the store does not yet hold A delivery-session retrospective (2026-09-16) found four habits the skills stated only where the wrong reader would see them, or not at all: - rdd-deliver step 4 read "repeat until TODO" with no round bound, while the bound lived only in rdd-cold-review and PROCESS.md — the reviewer's text, not the orchestrator's. The session ran a third round on its own call. The loop now carries the bound and the stop. - rdd-plan step 4 asked that claims be verified by reading the code, but a packet still stated a stale-bound constant from its definition while the agent path applied a different value. A stated value is read at the call site that applies it. - rdd-plan step 7 and rdd-build step 9: a bookkeeping push after the cold-review verdict moved the packet fingerprint twice and voided the review. The packet is finished before the verdict, and build progress is recorded as evidence, never as an edit to the reviewed packet. - rdd-start discipline: the human had to ask "what is not yet in the store?" to learn that two items were being held back. A pass report now names what the session holds that the store does not. No PROCESS.md rule changes; each line applies a rule that already exists. Co-Authored-By: Claude Fable 5.1 <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.
Why
A delivery-session retrospective (2026-09-16) found four habits that the skills state only where the wrong reader sees them, or not at all. None is a new process rule; each line applies a rule
PROCESS.mdalready holds.What changes
rdd-deliverstep 4 — the loop read "repeat untilTODO" with no round bound. The bound lived only inrdd-cold-reviewandPROCESS.md§Planning and readiness: the reviewer's text, not the orchestrator's. The session ran a third cold-review round on its own call. The loop now carries the bound and the stop: after a secondFAIL, hand what is known to the human.rdd-planstep 4 — a packet stated a 5-minute stale bound read from a constant's definition; the agent path applied 10 minutes and the 5-minute constant was unused. A stated value is now read at the call site that applies it, not at its definition (the same rulerdd-auditgives for quoted expressions).rdd-planstep 7 andrdd-buildstep 9 — a bookkeeping push (a code citation, a built-at note) after the cold-review verdict moved the packet fingerprint and voided the review, twice. The packet is finished before the verdict; which edits move the fingerprint is the store's decision, not the editor's intent. Build progress is recorded as evidence, never as an edit to the reviewed packet.rdd-startsession discipline — the human had to ask "what is not yet in the store?" to learn two items were being held back. A pass report names what the session holds that the store does not.Not changed
PROCESS.md,rdd-cold-review(its round bound was already right),file-state/.🤖 Generated with Claude Code