CoAgnes Labthe study spaceresearch preview · build 1ececa2

The machine, one change at a time

Fragments

A fragment is the smallest real run of the machine that shows one movement: a handful of records, and every change of state they caused — each one explained, each one tied to the record that caused it, to the template it belongs to, and to what it formed.

A recorded session shows a whole study; a fragment shows one gear turning. The machine ran each fragment for real, and its journal kept every write to every register — the registers the specification names. Atlas, the map of the whole run, stands beside every record, with that record selected.

The approach, drawn: One listener, one doer, one noteAn isometric construction drawing of the machine this fragment runs: the log as 5 slabs, #0 to #4; the listener note.gate above #2, which it hears; the readiness it writes as #3; the doer note.echo above it, which releases #4. Dimensions mark the two waves and the whole log; notes give the counts of the run.#0#1#2#3#4note.gatelistenernote.echodoernote.givensys.knot.readynote.echoedwave 1 · #0–#1wave 2 · #2–#4the log · 5 records · #0–#4Notes1. 31 changes of state, each journalled2. 14 functions of the state protocol3. 2 waves; quiet after #4
Fig. 00The approach, drawn — one listener, one doer, one notedrawn from the run fragment-one-knot-one-bind · after the amber draft (design 00 §6): named, never traced
  1. Fragment 1One listener, one doer, one noteone knot · one bind · one ingressThe smallest real run of the machine, one change at a time: a listener, a doer and one note. For every change, what you see and the line of code that made it.5 records31 changes of state2 wavesrun on 22 September 2026 · build 043cc8b
  2. Fragment 2One listener, one doer, one crossingone knot · one bind · one crossingThe smallest run in which the machine asks the world: a listener hears a note, a doer turns it into a request, and the answer comes back as a record.6 records37 changes of state2 wavesrun on 22 September 2026 · build 043cc8b
  3. Fragment 3One listener, one doer, one Cellone knot · one bind · one CellA whole Cell, the smallest: opened at the first fragment's slot, admitted, worked, assessed, reviewed by a person, sealed, and returned into the slot as a note.44 records238 changes of state5 wavesrun on 22 September 2026 · build 043cc8b

§How a fragment is told

  • The machine's own board. Each fragment is laid out the way the machine works: its log on the right, one record in the centre, what that record released on the left.
  • One record, one page. A record's page says where it came from — a person, the machine or the world — and shows every change of state it caused, in the order the machine made them: read as a story, or step by step, as in a debugger.
  • What it carries. Every kind of record is described field by field, with the section of the specification that defines it.
  • The code beside the change. The first time a function changes the state, its lines are shown — taken from the build that ran, never typed.
  • Real, small, complete. Every fragment was run for real, and ends when the machine is quiet — when a record causes no change at all.

The book's Part 3 — The Minimal Fragment tells the first movement in words.