Wave 4 · Inside the Cell · record #30domain.factcell@20::knowledge.l1
#30 · the private result
CellSpace records it as the Cell's result, moves the Cell to awaiting assessment, and writes its public mark as #31.
Came fromthe machineThe machine wrote it while the engine took #29: the inner doer acted — a local action, inside the Cell. step 167
when the engine took #30
168The engine takes #30ENGINE.CURSOR · propagate
a wave is settlingengine: working on #30membrane: 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
- end of the log
The engine What before after pointer — the next record to take #30 #31 The engine moves on to #30, the Cell's private result.
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
- #30 ·
ENGINE.CURSOR · propagate· offset: 30 · by engine - Picture
- pointer — the next record to take: #30 → #31
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)
169CellSpace records the Cell's resultCELL.STATE,CELL.RESULT · record-result
a wave is settlingengine: working on #30membrane: 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
- end of the log
cellspace/cell:cell@20 What before after state “running” “awaiting_assessment” resultValue none text = “A Cell is a bounded study the machine opens when a slot needs more th…” localResultOffset none 30 resultOffset none 30 CellSpace recognises the release as the Cell's result — the blueprint named its doer and type — records where it stands and moves the Cell to awaiting assessment: made, not yet trusted.
Where it happens
recordCellResult()Vol. 12 §5.3Records a Cell's result and moves the Cell to awaiting assessment: made, not yet trusted.
- Specification
- Vol. 12 §5.3
- Code
recordCellResult()incore/registers/record-cell-result.ts, line 15: the Cell now awaits its assessment- Journal
- #30 ·
CELL.STATE,CELL.RESULT · record-result· state: awaiting_assessment, resultOffset: 30 · by cellspace - Picture
- state: “running” → “awaiting_assessment”
core/registers/record-cell-result.ts· build 043cc8b// The result transition (Vol. 12 §5.3): the declared producer's delegated// publication moves the Cell from `running` to `awaiting_assessment` with// the result fields in one movement — runtime success, distinct from// assessment and from human usefulness (the four verdicts never collapse).import type { CellRegisters } from "./cell-registers";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";export function recordCellResult(file: RegisterFile,cell: CellRegisters,result: { offset: number; value: unknown }): void {cell.state = "awaiting_assessment";↑ the Cell now awaits its assessmentcell.localResultOffset = result.offset;cell.resultValue = result.value;cell.resultOffset = result.offset;↑ where its result stands in the logrecordTransition(file, `cellspace/cell:${cell.cellRef}`, "CELL.STATE,CELL.RESULT", "record-result", {↑ the change is written into the journalstate: cell.state,resultOffset: result.offset});}
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)
170The result's public mark enters as #31LOG · append
a wave is settlingengine: working on #30membrane: 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, markednew
- end of the log
The log What before after records in the log 31 32 #31 — the result, marked · cell.resultCellSpace writes the public mark of the private result as #31,
cell.result— readable at root. A Cell speaks outward only through the marks CellSpace writes.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
- #30 ·
LOG · append· offset: 31, kind: domain.fact · by engine - Picture
- records in the log: 31 → 32
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 #30
185The membrane passes #30MEMBRANE.CURSOR · sweep
a wave is settlingengine: at the endmembrane: passing #30
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 #30 #31 #30 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
- #30 ·
MEMBRANE.CURSOR · sweep· offset: 30 · by membrane - Picture
- pointer — the next record to pass: #30 → #31
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 Cell's private result
The inner doer's release, private to the Cell: its type carries the Cell's name, so no listener at root can hear it.
#30domain.factcell@20::knowledge.l1 the machine
| envelope | |
|---|---|
offset | 30Its 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@20::knowledge.l1The private type: the Cell's name before the result's type. |
| payload.data | |
bindId | cell@20::l1.seeking.releaseThe inner doer. |
uid | cell@20::l1.seeking.release#1Its intention's name. |
| payload.data.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.»The result: the person's words, released. |
end · #30
In the specificationVol. 03 §1Vol. 03 §5Vol. 12 §4Vol. 12 §5.3
Names it shares with other records
cell@20::l1.seeking.release— also on #23 inner doer
The record as the machine keeps it
{
"offset": 30,
"kind": "domain.fact",
"key": "fragment-one-cell",
"payload": {
"factType": "cell@20::knowledge.l1",
"data": {
"bindId": "cell@20::l1.seeking.release",
"uid": "cell@20::l1.seeking.release#1",
"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."
}
}
}
}