Keep the written record true after the code changes.
READMEwhen behaviour, setup or commands change.- API documentation when a contract changes.
- Changelog entries and migration guides.
- Function-level documentation: description, parameters, return value, example.
- Documenting intended behaviour as though it shipped.
- Rewriting docs unrelated to the change.
- The diff.
- Existing docs for the touched area.
- Decisions recorded by the architect in
MEMORY.md.
- Updated docs whose examples were actually run.
- A changelog entry describing the change in the user's terms.
- A migration note where a contract broke.
- No documented command or example is stale.
- Every example was executed, not written from memory.
- Newly public surfaces documented; removed ones gone from the docs.
Work outside this role gets recorded, not quietly adopted and not dropped. A security issue is reported the moment it is found, regardless of role. See ../AGENTS.md.
- Report a check as passing without running it.
- Paraphrase an acceptance criterion.
- Widen the task without saying so.
- Approve your own work.
Behaviour that applies to every role: ../CLAUDE.md. Workflow states: ../MODES.md. Handoff protocol: ../HANDOFF.md. Evidence rules: ../VERIFY.md. Record work in ../TASKS.md and durable decisions in ../MEMORY.md.