Wave 4 · Inside the Cell · record #31domain.factcell.result
#31 · the result is marked
Assess · result, sown at #8 to hear it, keeps it and announces it as #32.
Came fromthe machineThe machine wrote it while the engine took #30: CellSpace marked the Cell's result. step 170
when the engine took #31
171The engine takes #31ENGINE.CURSOR · propagate
a wave is settlingengine: working on #31membrane: waiting at #28
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- end of the log
The engine What before after pointer — the next record to take #31 #32 The engine moves on to #31 — the result's public mark, back at root.
Where it happens
takeNextTuple()Vol. 02 §4.1The engine's step: take the record under its pointer and move the pointer on — or stop, if the pointer has reached the end.
- Specification
- Vol. 02 §4.1
- Code
takeNextTuple()incore/registers/take-next-tuple.ts, line 15: at the end of the log, the engine stops- Journal
- #31 ·
ENGINE.CURSOR · propagate· offset: 31 · by engine - Picture
- pointer — the next record to take: #31 → #32
core/registers/take-next-tuple.ts· build 043cc8b// ENGINE.CURSOR advance (Vol. 02 §4.1) — the machine's instruction pointer:// returns the tuple at the cursor and moves it forward exactly once, or null// at quiescence. Advancing IS the context switch: the ambient wave context// moves to the propagated tuple in the same movement, so every transition// journalled during its propagation is attributed to it — the cube's spine.// The cursor never rewinds.import type { WaveTuple } from "../wave/gate";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";import { setDriver, setWaveContext } from "./set-wave-context";export function takeNextTuple(file: RegisterFile): WaveTuple | null {const engine = file.registers.engine;if (engine.cursor >= engine.base + engine.window.length) return null;↑ at the end of the log, the engine stopsconst tuple = engine.window[engine.cursor - engine.base];engine.cursor += 1;↑ the engine's pointer moves on by onesetWaveContext(file, { offset: tuple.offset, phase: "propagate" });setDriver(file, "engine");recordTransition(file, "engine", "ENGINE.CURSOR", "propagate", { offset: tuple.offset });↑ the change is written into the journalreturn tuple;}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in 6730f58 (2026-09-13)
172Assess · result opens a laneCLEWS · open-clew
a wave is settlingengine: working on #31membrane: waiting at #28
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- end of the log
The listener admit.note.gate--l1.seeking.assess.resultWhat before after lane · this session — open #31 is what the listener assess · result was sown to hear at #8. It opens a lane for this session.
Where it happens
ensureClew()Vol. 02 §4.2 · Vol. 03 §5.1Opens a lane in a listener for a new key — the first time a fact with that key reaches it.
- Specification
- Vol. 02 §4.2 · Vol. 03 §5.1
- Code
ensureClew()incore/registers/ensure-clew.ts, line 15: a new lane is opened for this key- Journal
- #31 ·
CLEWS · open-clew· key: fragment-one-cell · by knot:admit.note.gate--l1.seeking.assess.result - Picture
- lane · this session: — → open
core/registers/ensure-clew.ts· build 043cc8b// CLEWS lane creation (Vol. 02 §4.2): a clew is created lazily on the first// tuple of its key — parallel keys wind independent understanding (Vol. 05// §2, Vol. 03 §5.1). Creation is a transition (journalled); an existing lane// is a read and passes through silently.import type { ClewHandle, ClewRegisters } from "./topology-registers";import { recordTransition } from "./record-transition";export function ensureClew(clew: ClewHandle, init: () => ClewRegisters): ClewRegisters {const lanes = clew.region.clews.get(clew.knotId);if (!lanes) throw new Error(`Clew bank missing for knot '${clew.knotId}' — registration must precede facts (Vol. 02 §5.1).`);let registers = lanes.get(clew.key);if (!registers) {registers = init();lanes.set(clew.key, registers);↑ a new lane is opened for this keyrecordTransition(clew.file, `topology:${clew.region.regionId}/clew:${clew.knotId}`, "CLEWS", "open-clew", {↑ the change is written into the journalkey: clew.key});}return registers;}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in f36e70d (2026-08-18)
173Assess · result keeps the resultCOLLECTED · collect
a wave is settlingengine: working on #31membrane: waiting at #28
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- end of the log
The listener admit.note.gate--l1.seeking.assess.resultWhat before after lane · this session · slot seen empty cellRef = “cell@20” · result = {"text":"A Cell is a bounded study the machine opens when a slot needs more than a fact: it has its own charter, its own knots and binds, and a result that is assessed and reviewed before anything returns."} · localResultOffset = 30 · producedBy = {"bindId":"cell@20:: l1.seeking.release","uid":"cell@20::l1.seeking.release#1"}The Cell's result goes into the slot seen. Its condition holds: the evaluator's second need is about to be met.
Where it happens
collectDeterministicSlot()Vol. 02 §4.4 · Vol. 05 §3.3Fills a slot of a listener with a value it heard.
- Specification
- Vol. 02 §4.4 · Vol. 05 §3.3
- Code
collectDeterministicSlot()incore/registers/collect-deterministic-slot.ts, line 20: the slot is filled- Journal
- #31 ·
COLLECTED · collect· key: fragment-one-cell, slot: seen, reduce: latest · by knot:admit.note.gate--l1.seeking.assess.result - Picture
- lane · this session · slot seen: empty → cellRef = “cell@20” · result = {"text":"A Cell is a bounded study the machine opens when a slot needs more than a fact: it has its own charter, its own knots and binds, and a result that is assessed and reviewed before anything returns."} · localResultOffset = 30 · producedBy = {"bindId":"cell@20::
l1.seeking.release","uid":"cell@20::l1.seeking.release#1"}
core/registers/collect-deterministic-slot.ts· build 043cc8b// COLLECTED write (Vol. 02 §4.4, Vol. 05 §3.3): the deterministic knot's// slot fills — `append` accumulates an array, otherwise the newest value// stands. The condition never runs here; this op records the landing.import type { DeterministicClewRegisters, ClewHandle } from "./topology-registers";import { recordTransition } from "./record-transition";export function collectDeterministicSlot(clew: ClewHandle,registers: DeterministicClewRegisters,slot: string,reduce: string,value: unknown): void {if (reduce === "append") {const existing = registers.collected.get(slot);if (Array.isArray(existing)) existing.push(value);else registers.collected.set(slot, [value]);} else {registers.collected.set(slot, value);↑ the slot is filled}recordTransition(clew.file, `topology:${clew.region.regionId}/clew:${clew.knotId}`, "COLLECTED", "collect", {↑ the change is written into the journalkey: clew.key,slot,reduce});}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in f36e70d (2026-08-18)
174The slot is emptied againCOLLECTED · reset
a wave is settlingengine: working on #31membrane: waiting at #28
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- end of the log
The listener admit.note.gate--l1.seeking.assess.resultWhat before after lane · this session · slot seen cellRef = “cell@20” · result = {"text":"A Cell is a bounded study the machine opens when a slot needs more than a fact: it has its own charter, its own knots and binds, and a result that is assessed and reviewed before anything returns."} · localResultOffset = 30 · producedBy = {"bindId":"cell@20:: l1.seeking.release","uid":"cell@20::l1.seeking.release#1"}empty The listener empties its slot before it announces that it is ready; the result travels with the announcement.
Where it happens
resetDeterministicClew()Vol. 02 §4.4Empties a listener's slots once it has announced that it is ready.
- Specification
- Vol. 02 §4.4
- Code
resetDeterministicClew()incore/registers/reset-deterministic-clew.ts, line 9: the slots are emptied- Journal
- #31 ·
COLLECTED · reset· key: fragment-one-cell · by knot:admit.note.gate--l1.seeking.assess.result - Picture
- lane · this session · slot seen: cellRef = “cell@20” · result = {"text":"A Cell is a bounded study the machine opens when a slot needs more than a fact: it has its own charter, its own knots and binds, and a result that is assessed and reviewed before anything returns."} · localResultOffset = 30 · producedBy = {"bindId":"cell@20::
l1.seeking.release","uid":"cell@20::l1.seeking.release#1"} → empty
core/registers/reset-deterministic-clew.ts· build 043cc8b// The deterministic reset rule (Vol. 02 §4.4): COLLECTED clears at readiness// unless the policy says `never` — the station holds the policy, this op// holds the movement.import type { DeterministicClewRegisters, ClewHandle } from "./topology-registers";import { recordTransition } from "./record-transition";export function resetDeterministicClew(clew: ClewHandle, registers: DeterministicClewRegisters): void {registers.collected = new Map();↑ the slots are emptiedrecordTransition(clew.file, `topology:${clew.region.regionId}/clew:${clew.knotId}`, "COLLECTED", "reset", {↑ the change is written into the journalkey: clew.key});}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in f36e70d (2026-08-18)
175The readiness enters the log as #32LOG · append
a wave is settlingengine: working on #31membrane: waiting at #28
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- #32readinessnew
- end of the log
The log What before after records in the log 32 33 #32 — readiness · sys.knot.readyAssess · result's announcement is written at the end of the log as #32.
Where it happens
appendEmissions()Vol. 02 §4.1 · Vol. 03 §1The only function that adds records to the log. Each new record gets the next free number, at the end.
- Specification
- Vol. 02 §4.1 · Vol. 03 §1
- Code
appendEmissions()incore/registers/append-emissions.ts, line 14: the new record gets the next free number- Journal
- #31 ·
LOG · append· offset: 32, kind: sys.knot.ready · by engine - Picture
- records in the log: 32 → 33
core/registers/append-emissions.ts· build 043cc8b// The one LOG writer (Vol. 02 §4.1, Vol. 03 §1): emissions become tuples by// receiving the next dense absolute offset — `base + window.length` — and// nothing else ever grows the log. Each append is journalled under the// ambient context, so a batch born of a propagated tuple carries that// tuple's offset as its cause — the cube's provenance line (ADR-002).import type { WaveEmission, WaveTuple } from "../wave/gate";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";export function appendEmissions(file: RegisterFile, emissions: readonly WaveEmission[]): void {const engine = file.registers.engine;for (const emission of emissions) {const tuple: WaveTuple = { ...emission, offset: engine.base + engine.window.length };↑ the new record gets the next free numberengine.window.push(tuple);↑ it is added at the end of the logrecordTransition(file, "engine", "LOG", "append", {↑ the change is written into the journaloffset: tuple.offset,kind: tuple.kind});}}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in f36e70d (2026-08-18)
when the membrane passed #31
186The membrane passes #31MEMBRANE.CURSOR · sweep
a wave is settlingengine: at the endmembrane: passing #31
The log - #0a listener
- #1a doer
- #2listener: the charter
- #3doer: the author
- #4listener: charter seen
- #5listener: blueprint seen
- #6doer: the planner
- #7listener: assess · charter
- #8listener: assess · result
- #9doer: the evaluator
- #10the charter wanted
- #11the blueprint
- #12readiness
- #13readiness
- #14a request: a charter
- #15the charter proposed
- #16the charter defined
- #17readiness
- #18readiness
- #19a request: a Cell
- #20the seed
- #21the Cell is open
- #22inner listener
- #23inner doer
- #24the Cell's context
- #25return listener
- #26return doer
- #27the return address
- #28the person's words
- #29readiness
- #30the private result
- #31the result, marked
- #32readiness
- #33a request: assess
- end of the log
The membrane What before after pointer — the next record to pass #31 #32 #31 asks nothing of the world, so the membrane's pointer simply moves on.
Where it happens
sweepNextTuple()Vol. 02 §4.6 · Vol. 07 §3The membrane's step: pass over the record under its pointer and move the pointer on — exactly once per record.
- Specification
- Vol. 02 §4.6 · Vol. 07 §3
- Code
sweepNextTuple()incore/registers/sweep-next-tuple.ts, line 16: the membrane's pointer moves on by one- Journal
- #31 ·
MEMBRANE.CURSOR · sweep· offset: 31 · by membrane - Picture
- pointer — the next record to pass: #31 → #32
core/registers/sweep-next-tuple.ts· build 043cc8b// MEMBRANE.CURSOR advance (Vol. 02 §4.6, Vol. 07 §3): the membrane's own// reading of the one log — the second reception of one publication, never a// second truth. The cursor advances exactly once per offset per machine:// the exactly-once discharge guarantee lives in this movement.import type { WaveTuple } from "../wave/gate";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";import { setDriver, setWaveContext } from "./set-wave-context";export function sweepNextTuple(file: RegisterFile): WaveTuple | null {const engine = file.registers.engine;const membrane = file.registers.membrane;if (membrane.cursor >= engine.base + engine.window.length) return null;const tuple = engine.window[membrane.cursor - engine.base];membrane.cursor += 1;↑ the membrane's pointer moves on by onesetWaveContext(file, { offset: tuple.offset, phase: "sweep" });setDriver(file, "membrane");recordTransition(file, "membrane", "MEMBRANE.CURSOR", "sweep", { offset: tuple.offset });↑ the change is written into the journalreturn tuple;}
AGPL-3.0-onlyThe Lab's demonstration environment, as this fragment ran it (build 043cc8b). The code may change, and may differ from the code of a working machine.
Nest VM core, incubated in the CoAgnes garden · build 043cc8b (2026-09-21) · this file last changed in 6730f58 (2026-09-13)
Choose a step in the stack — or press →.
A fact: the result, marked
CellSpace's public mark of a Cell's private result: readable at root, and for review — not yet trusted.
#31domain.factcell.result the machine
| envelope | |
|---|---|
offset | 31Its place in the log — the only address a record has. The engine gives it when the record is added, the next free number, and it never changes. |
kind | domain.factWhich of the four kinds of record the machine knows. The kind decides what the payload holds. |
key | fragment-one-cellThis session's lane. |
| payload | |
factType | cell.resultThe fact type — cell.result, written by CellSpace alone. |
| payload.data | |
cellRef | cell@20The Cell. |
result | textThe result. |
localResultOffset | 30Where the private result stands in the log. |
producedBy | bindId · uidThe doer and the intention that made it. |
end · #31
In the specificationVol. 03 §1Vol. 03 §5Vol. 12 §5.3
Names it shares with other records
The record as the machine keeps it
{
"offset": 31,
"kind": "domain.fact",
"key": "fragment-one-cell",
"payload": {
"factType": "cell.result",
"data": {
"cellRef": "cell@20",
"result": {
"text": "A Cell is a bounded study the machine opens when a slot needs more than a fact: it has its own charter, its own knots and binds, and a result that is assessed and reviewed before anything returns."
},
"localResultOffset": 30,
"producedBy": {
"bindId": "cell@20::l1.seeking.release",
"uid": "cell@20::l1.seeking.release#1"
}
}
}
}