| name | contract-change-control |
| description | Manage versioned amendments to a chapter's per-chapter contract during a rewrite cycle. Diffs pre vs post contract, requires a reason for every changed field, flags amendments that would mask Gate B failure (e.g., a `feels:` slot weakened to match the rewrite rather than its promise), and snapshots both versions into the chapter's audit history. Used by Wayne, Bonnie, and jerry-crew-chief at Gate B. |
| version | 1.0.0 |
Contract Change Control
Global Five Over-Rules
- Evidence before elegance. Never improve the story by weakening the evidence.
- Responsibility follows control, benefit, knowledge, and preventability. Do not stop at the most visible actor.
- Keep the taxonomy intact. Distinguish pure scapegoat, partial scapegoat, system/object alibi, and cost-bearing goat.
- Steelman before judgment. Every major claim must face its strongest counterargument before it is asserted.
- Handoff cleanly. Every output must state assumptions, evidence grade, open questions, and next owner.
When to use
- Whenever a chapter's
book/chapters-v2/<n>-<slug>.contract.yml is edited after the chapter has entered status: in-rewrite per rule 09.
- Before
/contract-audit runs on a chapter whose contract has changed since the prior audit — otherwise contract-audit grades against the moved goalpost.
- At Gate B, automatically, by jerry-crew-chief, to verify the contract the Gate B package presents is identical to the contract the rewrite was authorized against (or to verify any amendments meet the cited-reason requirement in this skill's rubric).
Context: Wayne completes the rewrite of ch-08 and discovers the chapter's actual `feels:` transition is `sympathy:split:installed`, not the declared `sympathy:chain:installed`. He amends the contract and runs `/contract-change-control`.
