How the Machine Thinks
This book is a map of the machine CoAgnes assembles: it lays out the whole territory — the general shape, not one instance of it — so that a reader who has never seen the system can arrive here first, build a working model of the whole, and only then go and watch it happen for real.
- 01Part 1 — System OverviewHow the machine works, seen as a whole — the log, listeners and doers, and the settle loop that drives them.
- 02Part 2 — Lines of ReasoningWhat forms a chain of analytical steps inside the system, and the one mechanism — represent — that carries a finding across any boundary.
- 03Part 3 — The Minimal FragmentThe smallest construct that runs, and the three ways a new one is authored.
- 04Part 4 — The Standard Analytical ScenarioThe nine moves common to every study on the shelf, worked in full for one real press-release study.
- 05Part 5 — Protocols and Integration PointsThe complete outward-facing surface of the system: every ingest type, every projection, every route.
- 06Part 6 — System Architecture and Component InterconnectionThe ringed architecture the codebase is built from, and one user action traced through every ring.
- 07Part 7 — The Cell — A Local Field of MeaningHow a delegated sub-investigation is opened, worked, confirmed or refused, and released.
- 08Glossary — the book's own termsThe terms this book coins or uses in its own way, each tied to a real example.
- 09Sources — every file the book citesEvery file the book draws on, gathered in one place for anyone who wants to check a claim against the repository.
§How the book is built
Seven parts, each its own numbered folder. Every part makes the identical journey, in the identical order — an idea in plain words, the standard analytical practice it mirrors, the machine's own specification for it, and finally the actual running code — and every part, across its four files, answers the same seven questions this book set out to answer:
| stage (the file to read) | the question it answers first |
|---|---|
| 1 · the idea | What are we doing here? |
| 2 · the analytical frame | How do we define and fill the gaps an ordinary system leaves open? |
| 3 · the specification | Where, and how, do flows actually form — and where do the key vectors that carry knowledge between one plane and another arise? |
| 4 · the technology | How exactly is this built, at the level of real functions and real tuples — and how can a person, and the machine itself, confirm any of it? |
One question runs underneath all four in every part rather than belonging to any single one of them: how does knowledge actually arise, as a structure, from doing research inside this system? The book's short answer, repeated in different clothes in every part: knowledge here is never loose text a model happened to produce — it is a tuple, of a declared shape, sitting at a fixed position in an append-only log, carrying its own status (declared, happened, unclear — 4.3), its own brief (a Charter — 7.3), and its own chain of custody back to a real person's decision (Part 7). "Structure" is not a metaphor here; it is the literal shape a finding is forced to take before the machine will let it be used anywhere else.
§Suggested reading order
Front to back is the intended order — each part leans lightly on the ones before it, most heavily Part 1's two ingredients and Part 3's minimal fragment. A reader in a hurry who already knows the system's rough shape can start at Part 7 or Part 4 instead and follow the links backward as needed; every cross-reference in the book points at a specific file, never just "elsewhere."