Concepts
Lifecycle: stub, assumed, validated, superseded
Every block says how proven it is: stub (a default), assumed (written for this project, not yet proven), validated (proven by research, a decision or production use) or superseded (replaced). The state is how people and AI know how far to trust a page.
Writing something down does not make it true, so the brain does not pretend it does. Each block carries one lifecycle state, and an AI reading the block gets it with the content.
The four states
| State | Means | How a block gets there |
|---|---|---|
| Stub | A default from the scaffold, not yet made specific to this project | Every entity starts here when a project is created |
| Assumed | Written for this project, but not proven: an assumption, named as one | Automatically, the first time a stub gets real content |
| Validated | Proven through research, a decision or production use | Only when that is true; claimed explicitly, ideally with the evidence linked |
| Superseded | Replaced by a newer block | A supersedes link from the newer block; the old one stays readable |
The order is stub → assumed → validated, and any of them can become superseded.
Why a stub is not a gap
A project that starts with thirty-four stubs is complete in shape on day one. The stub says what it is waiting for, and an AI reading it knows it is a default, not a fact about you. Treat stub as the floor, not the finish line: as soon as there is evidence, write the block and it moves to assumed.
Validated means proven
Only claim validated when something proves it: interviews behind a persona, an accepted decision, a KPI that is actually measured, a feature people use. Link the evidence with a supports link so the claim can be checked later. Agents are told the same in the connector's working rules: mark what is unproven as assumed, and claim validated only when it is true.
Where you see it
- Over MCP, every block from
get_blockcarries itsmaturity, andget_v3_overviewreturns the counts per state and the most mature state per entity. - On the Map, the selected block shows its state beside its number of connections.
- In the book, a page says something simpler that cannot drift: Not written, Default (still the starting text) or Written for this project, derived from the page itself. The project's front page counts the chapters written per group.
- In exports and dashboards, anything past stub counts as written.
Older names
Earlier versions called the second state drafted. Clients that still send drafted are accepted and read as assumed. The old status column (empty / draft / complete) and the percentages built on it are gone.
Next
- Writes, changes and locks: every state change is a write with a reason.
- Relations: linking the evidence behind a validated block.
- Writing for AI agents: how to write a block that earns its state.
Last updated: