System rules
Non-negotiables, one file per concern. CLAUDE.md links here rather than restating them, because a single growing file gets skimmed and then ignored.
| Rule | Covers |
|---|---|
| Attested ledger | The bank ledger a person checked against the PDFs is the source of truth; attested statements are frozen by trigger; unlock only on Alex's word |
| guardrails.md | What may become a creative, and why it is enforced in the database |
| verification.md | Why a passing build is not evidence anything works |
| cost.md | Where money is spent and what must never enter the hot path |
| skills.md | How the skill set stays coherent as it grows, and what to update when adding one |
| taste.md | Why output reads as slop, and the four structural commitments against it |
| depth.md | How much machinery a capability's quality needs, and the debt register |
| performance.md | Why speed is a correctness property, and why the build order is what it is |
| data-safety.md | Deletion guardrails, backup topology, and where Drive belongs |
| credentials.md | OAuth, rotation, and connections that must survive unattended |
| documentation.md | The register, SOPs, and what "Live" is allowed to mean |
Each states the rule, then why — the reasoning matters more than the rule, because it is what tells you whether a new situation is covered.
- frameio-never-deletes — Frame.io holds live client work; no delete path exists and a test keeps it that way