One verb, one shape
A persona is always six fields and a ledger; a decision always carries a falsifier with a date; evidence is always one signal, graded. The shape is what lets a page be a read instead of a rewrite.
boss from the records in demo/kettlewick/, the same way an install renders yours.
This is the part of BOSS that does the filing so the founder never has to. Nothing lives in the chat: what you say becomes a record in a folder, in a fixed shape, with an id and a status line — and the playbook, the design space and the board are reads of those folders, never documents anyone maintains. Change the work and the pages change; there is nothing else to update.
docs/A persona is always six fields and a ledger; a decision always carries a falsifier with a date; evidence is always one signal, graded. The shape is what lets a page be a read instead of a rewrite.
captured · ready · building · shipped · deferred · dropped — a word on the record's own frontmatter. The board reads it; nobody drags a card. A parked idea carries its re-open trigger in the same line.
15 verbs · lays down docs/evidence/ docs/ideas/ docs/source/ docs/team/ · its verbs write docs/decisions/ docs/personas/
24 verbs · its verbs write docs/ docs/ideas/ docs/competition/ docs/dossier/ docs/brand/ docs/design/ docs/design/components/ docs/design/icons/ docs/design/library/ docs/product/ docs/health/ docs/measure/ docs/trust/
2 verbs · adds no folder of its own
1 verbs · adds no folder of its own
Drop a deck in docs/source/ and BOSS says which records it could fill and writes each only when you say so. A field nobody answered stays a hole on the page — a confident answer arrived at with no information is worse than a blank.
One living doc per idea, a canvas that pressure-tests it, a build contract when it earns one, and every load-bearing call with the signal that would prove it wrong.
docs/ideas/IDEA-NNN — a living idea doc with a sharpening current shape and an append-only capture log; the canvas as thirteen cells; FEAT-NNN — the build contract with acceptance criteria and the paths that must not break
docs/decisions/DEC-NNN — context, decision, why, and a falsifier with a date; superseded, never edited
Who it is for as a persona with a ledger that says how much of it is real, and what real people actually said or did, graded — a compliment never reads as a receipt.
docs/personas/one persona per file: who, context, jobs, pains, values, what you don't know yet — and a ledger, synthetic vs real, that moves as evidence lands
docs/evidence/EVID-NNN — one signal per file, dated, graded stated-pain → observed-behavior → commitment, tied to the assumption it bears on
docs/team/one person per file — the specific thing seen, built, sold or lived; what they bring and don't; a role you need and don't have, written plainly
Rivals with a checked date and the honest "why they might win"; your own decks and reports, dated on the way in, so a figure from March is never a fact about today.
docs/competition/the field as one table, one file per rival with where it breaks and how they do it, every row with a checked date
docs/source/your own material — a deck, a report, a saved page — dated in the name; /import reads it and offers the records it could fill
docs/dossier/the mentors' positions, dated — the capital mentor's not-yet with its reason is what the playbook quotes as the ask
The brand as a living doc that starts nascent; the design system as tokens, a style guide, components with usage pages, patterns and flows — each with the decision that chose it.
docs/brand/the mark, when there is a file — the brand doc itself lives beside the devlog
docs/design/tokens.json, the style guide, components, patterns, flows, the reviews — the design space is a read of these
docs/design/components/one usage page per component, written at its review — when to use it, when not
docs/design/icons/the icon set as SVG files; the design page draws them from here and copies them as a sprite
docs/product/JOURNEY.md — the flows as a founder would walk them, written at the first flow
After the first user: one activation metric, one retention curve, a dated health verdict that defaults to pre-fit, and the trust page a buyer can read. The story so far, one entry a session.
docs/health/HEALTH-<date> — a verdict, dated: pre-fit by default, the curve when there is one, the one next move
docs/measure/MEASURE-<date> — the one activation metric, the one retention curve, at most ten events, the humane note
docs/trust/TRUST.md — what you collect, who processes it, how someone reaches you about their data; one honest paragraph
docs/the devlog (what landed, what surprised you, one entry a session), the brand doc, the resume the next session reads first
What BOSS installed for the host and the state it keeps for itself — local, never in the repo, and never the founder's to maintain.
.claude/agents, skills, hooks and rules for the host — laid down by mode, only what the venture has earned
.boss/the stamp, the config, the conscience's read on the venture, the rendered pages — machine state, gitignored