Why this shape suits analytical work

How do we define and fill systemic gaps.

§The gap most tools quietly carry

Ask most software "what actually happened here, in order, and why" and the honest answer is usually reconstructed after the fact — from server logs meant for debugging, from a database's current state with its history discarded, from a chat transcript that mixes the system's reasoning with its user-facing text. The system was never designed to answer that question; the answer is scavenged.

1.1's one list is a direct answer to that gap, made structural rather than scavenged: the record of what happened is the system, not a side effect of it. There is nothing to reconstruct because nothing was ever thrown away or summarised in the first place.

§Three standard analytical needs, met by construction

Provenance. Every finding a study produces can be traced to the specific entries that fed it — not "somewhere in this conversation," but a named position in an ordered list, forever. This is the same discipline a court exhibit, an audit workpaper, or a cited fact in a piece of journalism is held to: show your working, all the way down.

Reproducibility. Because nothing is ever edited or removed, replaying the same list from the start reconstructs the exact same state every time — which is what lets Part 4's worked example be checked by a second reader independently rather than taken on trust, and what lets Part 6's "readings" be thrown away and rebuilt at will with no loss.

A clean seam between drafting and deciding. Because listeners and doers only ever react — nothing acts on its own initiative outside what it was told to watch for — a human decision (accept this, attest that) is always a distinct, visible entry of its own, never folded silently into a machine step. 7.2 develops this into the specific shape of a delegated sub-task with a sign-off; here, it is worth naming as the general property underneath it: the list can always tell you which entries a person actually decided, and which ones a machine merely produced.

§What this trades away, honestly

A system built this way is not the fastest possible way to get an answer, and it is not free-form — you cannot simply "chat" your way to a result outside the shape of listeners waiting for specific things. Part 3 takes this trade-off head-on: the cost of every entry having a fixed, checkable shape is that nothing enters the list informally, and building a new capability means declaring, in advance, exactly what it will wait for and what it will do once it sees it. The next file, 1.3, gives that discipline its formal names.