Wave 4 · Inside the Cell · record #28domain.factcontext.given
#28 · the words enter the Cell
The level routes them into cell@20: the inner listener keeps them and announces it as #29; the Cell counts the effect.
Came froma personA person gave it at the door: the only material the Cell receives. step 153
when it came in at the door
153Record #28 enters the logLOG · append
a wave is settlingengine: next: #28membrane: 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 wordsnew
- end of the log
The log What before after records in the log 28 29 #28 — the person's words · context.givenThe door adds the person's words as #28: a fact of type
context.given, at the levell1.seeking.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
LOG · append· offset: 28, kind: domain.fact · by engine- Picture
- records in the log: 28 → 29
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 engine took #28
154The engine takes #28ENGINE.CURSOR · propagate
a wave is settlingengine: working on #28membrane: 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
- end of the log
The engine What before after pointer — the next record to take #28 #29 The engine's pointer moves past #28 — the only material the Cell receives, and a person gives it.
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
- #28 ·
ENGINE.CURSOR · propagate· offset: 28 · by engine - Picture
- pointer — the next record to take: #28 → #29
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)
155The inner listener opens a laneCLEWS · open-clew
a wave is settlingengine: working on #28membrane: 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
- end of the log
The listener cell@20:: l1.seeking.gateWhat before after lane · this session — open The words carry the level
l1.seeking, and that is what routes them into this Cell: the inner listener, in the region of cell@20, 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
- #28 ·
CLEWS · open-clew· key: fragment-one-cell · by knot:cell@20::l1.seeking.gate - 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)
156The inner listener keeps the wordsCOLLECTED · collect
a wave is settlingengine: working on #28membrane: 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
- end of the log
The listener cell@20:: l1.seeking.gateWhat before after lane · this session · slot text empty “A Cell is a bounded study the machine opens when a slot needs more than a fact: it has it…” The person's words go into the inner listener's slot text. Its condition holds: it has what it waits for.
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
- #28 ·
COLLECTED · collect· key: fragment-one-cell, slot: text, reduce: latest · by knot:cell@20::l1.seeking.gate - Picture
- lane · this session · slot text: empty → “A Cell is a bounded study the machine opens when a slot needs more than a fact: it has it…”
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)
157The slot is emptied againCOLLECTED · reset
a wave is settlingengine: working on #28membrane: 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
- end of the log
The listener cell@20:: l1.seeking.gateWhat before after lane · this session · slot text “A Cell is a bounded study the machine opens when a slot needs more than a fact: it has it…” empty The inner listener empties its slot before it announces that it is ready; the words travel 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
- #28 ·
COLLECTED · reset· key: fragment-one-cell · by knot:cell@20::l1.seeking.gate - Picture
- lane · this session · slot text: “A Cell is a bounded study the machine opens when a slot needs more than a fact: it has it…” → 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)
158The Cell counts an effect: 1CELL.EMISSIONS · count-effect
a wave is settlingengine: working on #28membrane: 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
- end of the log
cellspace/cell:cell@20 · appears What before after cellRef — “cell@20” key — “fragment-one-cell” policy — mode = “trial” · isolation = “subscribed” · raw_input = “deny” · accepts = [{"match_type":" context.given"}] · capabilities = ["inference"] · budget = {"max_records":2,"max_emissions":120,"max_inference_calls":12} · publish = {"candidate":"knowledge.l1","accepted":"knowledge.l1.accepted"}resultType — “cell@20:: knowledge.l1”producerBind — “cell@20:: l1.seeking.release”plannerBindId — “ admit.note.gate--l1.seeking.planner”plannerUid — “ admit.note.gate--l1.seeking.planner#1”state — “running” emissions — 1 inferenceCalls — 0 resultValue — none localResultOffset — none resultOffset — none charterRef — “charter@15” assessedOffset — none aggregate — none Every effect inside a Cell is counted against its budget. The count is 1: the readiness about to be announced. A Cell over its budget is stopped by CellSpace, not by judgement.
Where it happens
countCellEffect()Vol. 12 §8Counts one effect of a Cell against its budget — every readiness and every release inside it.
- Specification
- Vol. 12 §8
- Code
countCellEffect()incore/registers/count-cell-effect.ts, line 15: one more effect is counted- Journal
- #28 ·
CELL.EMISSIONS · count-effect· count: 1 · by cellspace - Picture
- cellRef: — → “cell@20”
core/registers/count-cell-effect.ts· build 043cc8b// Cell budget counters (Vol. 12 §8–9): every locally returned emission and// every inference/service intention counts pre-interception — the ceilings// are judged by the station against the Cell's policy; this op is the// counting itself, returning the new total.import type { CellRegisters } from "./cell-registers";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";export function countCellEffect(file: RegisterFile,cell: CellRegisters,counter: "emissions" | "inferenceCalls"): number {cell[counter] += 1;↑ one more effect is countedrecordTransition(↑ the change is written into the journalfile,`cellspace/cell:${cell.cellRef}`,counter === "emissions" ? "CELL.EMISSIONS" : "CELL.INFERENCE_CALLS","count-effect",{ count: cell[counter] });return cell[counter];}
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)
159The readiness enters the log as #29LOG · append
a wave is settlingengine: working on #28membrane: 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
- #29readinessnew
- end of the log
The log What before after records in the log 29 30 #29 — readiness · sys.knot.readyThe inner listener's announcement is written at the end of the log as #29 — in the Cell's name.
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
- #28 ·
LOG · append· offset: 29, kind: sys.knot.ready · by engine - Picture
- records in the log: 29 → 30
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 #28
183The membrane passes #28MEMBRANE.CURSOR · sweep
a wave is settlingengine: at the endmembrane: passing #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
- #32readiness
- #33a request: assess
- end of the log
The membrane What before after pointer — the next record to pass #28 #29 #28 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
- #28 ·
MEMBRANE.CURSOR · sweep· offset: 28 · by membrane - Picture
- pointer — the next record to pass: #28 → #29
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 person's words, for the Cell
The material a person gives a Cell: words at the Cell's level. The level is what routes them into this Cell and no other.
#28domain.factcontext.given a person
| envelope | |
|---|---|
offset | 28Its 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 | context.givenThe fact type — context.given, which the Cell accepts. |
| payload.data | |
level | l1.seekingThe level: the Cell's inner listener hears only this one. |
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.»The person's words. |
end · #28
In the specificationVol. 03 §1Vol. 03 §5Vol. 04 §3.1Vol. 07 §6Vol. 12 §4
The record as the machine keeps it
{
"offset": 28,
"kind": "domain.fact",
"key": "fragment-one-cell",
"payload": {
"factType": "context.given",
"data": {
"level": "l1.seeking",
"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."
}
}
}