docs(prose-tests): the record catches up with day two - #588
Merged
Conversation
CLAUDE.md still told a case author to run until state lands — the rule P9 overturned when a handoff proved as deterministic an ending as a delta, and the exact instruction that would have pushed short entry walks into needing conversation stubs. It now states the current rule, lists calls_in_order among the invariants, and names conduct and claims mode in the case anatomy, so an agent working from CLAUDE.md alone authors to the contract as it is. The prose-test README gains the two pieces day two added and one it never had: a Playing the User section covering answers and conduct — the arrival-order hazard that forbids mixing them around an interview, the pin-choices-with-invariants rule, and the P4 boundary extended to roleplay — and the files[] guidance rewritten from what was learned measuring it: harvested from walks not link-crawls, a ratchet across runs, opened-is-not-walked. The design log gains P11, naming conduct as contract rather than convenience, and the day-two entry: the closing-turn race, writes as evidence, the whole-phase quick-fix case, defects five through seven with the recurring pattern named — a guard keyed on artifact content an earlier step writes is suspect — and the forty-PR landing. Co-Authored-By: Claude Opus 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.
Summary
Three documentation surfaces brought current with the landed programme — one of them was actively wrong.
calls_in_orderto the invariants list, and namesconductandworld: "claims"in the case anatomy — so an agent working from CLAUDE.md alone authors to the contract as it is.tests/prose/README.mdgains a Playing the User section (answersvsconduct, the arrival-order hazard that forbids mixing them around an interview, pin-choices-with-invariants, the P4 boundary extended to roleplay) and rewrittenfiles[]guidance from what measuring it taught: harvest from walks not link-crawls, ratchet across runs, opened ≠ walked.design/prose-tests.mdgains P11 — conduct as contract, not convenience — and the day-two Log entry: the closing-turn race, writes-as-evidence, the whole-phase quick-fix case, defects five–seven with the recurring pattern named (a guard keyed on artifact content an earlier step writes is suspect), and the forty-PR landing.Deliberately excluded: the CONVENTIONS.md guard rule — that's a convention decision awaiting Lee's call, not documentation of something already agreed.
Test plan
🤖 Generated with Claude Code