The minimal fragment, and how it is developed
What this part is for. Part 1 said the whole machine is built from exactly two ingredients — a listener and a doer. This part takes that claim seriously and follows it to its practical end: what is the smallest possible pairing of the two that actually does something, and — because nothing in this system exists until someone declares it — what does it actually take, in practice, to bring a new one into being? Three different answers to that second question turn out to be the same answer underneath, and this part shows why.
The one-sentence version: nothing about a Cell, a whole study, or an entire delegated investigation is a different kind of thing from one listener waiting for one fact and one doer reacting to it — everything bigger is that same pair, repeated and wired together, never a new construct.
- 013.1 OverviewThe smallest thing that runs — one listener and one doer — read whole from the real example the codebase keeps and tests.
- 023.2 Analytical RationaleWhy the smallest unit of a study is one question plus one action, in ordinary research terms.
- 033.3 Functional SpecificationThe three ways a fragment is authored, and why the machine trusts none of them until they prove themselves.
- 043.4 Technical ImplementationThe actual functions that check, register and — in one case — assemble a fragment live.