Fragment 2 · one knot · one bind · one crossing
One listener, one doer, one crossing
The first fragment's listener, and a doer that does not act by itself: it asks. The request leaves the machine as a record of its own log, the world answers, and the answer comes back as a record too — joined to the request by the same two names.
What you will see
- How the machine asks the world: the doer writes a request into its own log, the membrane hands it out, and the answer comes back as a record.
- Every change of its state, before and after, in the order it happened — 37 of them.
- The 17 functions that made those changes — three of them new since the first fragment: the membrane's hand-out and its return.
Contents
Words you will meet
- log
- The list of records the machine keeps. Records are only added at the end; nothing in it is ever changed.
- record
- One line of the log, numbered from #0. The specification calls it a tuple.
- wave
- Everything that happens between two quiet moments: something is added at the door, and the machine reacts until nothing is left to do.
- engine
- Takes each new record in turn and lets the machine react to it. Its pointer never goes back.
- membrane
- The machine's edge. After the engine, it passes over every new record and hands anything addressed to the outside world to it.
- register
- A named place where the machine keeps part of its state between records. The specification names every one (Vol. 02 §4).
- station
- A part of the machine that owns some registers: the engine, the membrane, a listener, a doer.
- journal of changes
- The machine's own record of every write to a register, with the function that made it. Not to be confused with a journal knot, a pattern of the specification.
- listener — the machine says knot
- Waits for facts of the kinds it was told to hear, keeps them in slots, and announces when it has enough.
- slot
- A named place in a listener where a heard value is kept.
- lane
- A listener or a doer keeps a separate lane for every key, so that different conversations never mix. Here the key is this session.
- readiness
- A listener's announcement that it has enough — itself a new record in the log.
- doer — the machine says bind
- Waits for the listeners it depends on, then acts once.
- rendezvous
- A doer's gathering place: which listeners have spoken, and what they said.
- intention
- What a doer sets out to do, under a unique name, so that its result can be traced back to it.
- the world
- Everything outside the machine. The machine never calls it: it writes what it wants into its own log, and what the world answers comes back as a record.
- request
- What a doer writes into the log when it needs the world: what to do, about what, and in which shape the answer must come. The specification calls it a service request.
- controller
- The world's only station. It claims a request by its shape, does what is asked, and its answer comes back through the membrane as a record. Here it is a stand-in that answers in the right shape and names itself.
- answer
- What the world returns, written into the log under the type the doer asked for, carrying the doer's name and the intention's name — so that the request and its answer stay joined.
About this recording
- The run
- store
fragment-one-crossing-det, 2026-09-22 · 6 records, 2 waves, 37 changes of state - The code
- build
043cc8bof 2026-09-21 · 17 functions, taken by the instrument, never typed - The machine
- class
deterministic· none — the world here is the schema double, the deterministic class's stand-in: it answers any request that carries a shape with a result of that shape that names itself (“[deterministic class] answer · from: …”). No model was asked. The log reads the same as it would with a model behind the membrane; only the answer's words differ - By hand
- the door of the garden's deterministic stand (port 3313), by hand: the two records through
records, the note throughfacts - Written by
- run by an AI assistant (Claude Fable 5.1) on 22 September 2026; the notes of this form written by Claude Opus 5.5 on 27 September, checked against the journal; the code is taken by the instrument, never typed
- As data
- the fragment · its reading · Atlas