content-machinelisted

# Content Machine The machine does not write from a topic. It interviews the author, then shapes what he actually said. Everything below exists to keep that constraint enforced. Background and the public/private split: [`creative-studio/content-machine/README.md`](../../../creative-studio/content-machine/README.md). Build map: [GitHub #158](https://github.com/seanwinslow28/code-brain/issues/158). ## Runtime-impact rulings A **runtime-impact ruling** is a ratified decision that adds, removes, changes, or moves behavior in the live machine. It is not complete when only its ticket, map, or reference record is correct; it is complete when every operating file that loads or enforces the behavior agrees with it. Every runtime-impact ruling therefore has two minimum checks: a human impact inventory that names the live consumers and verifies each required update, plus a mechanical retirement check whenever the ruling makes an existing instruction, term, or route invalid. The mechanical check is a floor: it can find retired vocabulary, but it cannot prove that a rule runs at the right stage. **Scope:** the Content Machine operating surface — this skill, Content Oracle, and every skill or file the machine directly loads or invokes. Unrelated skills elsewhere in `.claude/skills/` are outside this check until evidence justifies widening it. Mechanical retirement rules live in one canonical registry at `runtime-retirements.toml` beside this file. Each record names the retirement's