intent-tracelisted

# Intent trace This team writes the PRD, derives acceptance criteria from its own PRD, implements against its own spec, and tests against its own criteria. **It can prove conformity to its interpretation and nothing else.** If the interpretation drifted, everything downstream is consistently, verifiably, greenly wrong. Nothing in here fixes that by being read. It fixes it by making the derivation *nameable*: every node says where it came from and who checks it, and two scripts fail when the chain does not hold. ## 1. The founder record — `docs/00-founder-intent/` The original brief, transcripts, examples, competitor references and constraints **exactly as received**. Derived documents evolve; this one does not. ``` docs/00-founder-intent/ README.md what this directory is, copied from the plugin brief.md the founder's words, verbatim, dated transcript-<date>.md a conversation, pasted whole example-<name>.<ext> a screenshot, a competitor link, a spreadsheet they sent constraints.md budget, deadline, platform, legal, "never do X" decisions.md append-only founder decisions (see §5) MANIFEST.sha256 the tamper record — written by scripts/founder-intent.mjs ``` **Rules:** - **Append-only.** Correcting the founder's words is not editing, it is losing the only external oracle the team has. A changed mind is a *new* dated entry in `decisions.md`, never an edit. - **Verbatim.** Summarised intent is interpreted intent, whic