Wave 2 · The opening · record #23sys.descriptor.defined
#23 · the Cell's inner doer
It is registered in the Cell's own region. The Cell's figure is complete.
Came fromthe machineThe machine wrote it while the engine took #20, right after the inner listener. step 121
when the engine took #23
127The engine takes #23ENGINE.CURSOR · propagate
a wave is settlingengine: working on #23membrane: waiting at #20
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
- end of the log
The engine What before after pointer — the next record to take #23 #24 The engine moves on to #23 — the Cell's inner doer, written by the machine.
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
- #23 ·
ENGINE.CURSOR · propagate· offset: 23 · by engine - Picture
- pointer — the next record to take: #23 → #24
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)
128The inner doer is added — in the Cell's regionBIND.DEFS · register-descriptor
a wave is settlingengine: working on #23membrane: waiting at #20
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
- end of the log
The figure of cell@20 What before after doer cell@20:: l1.seeking.release— acts on cell@20:: l1.seeking.gate; releases cell@20::knowledge.l1(release@1)when cell@20:: l1.seeking.gateis ready, it wakes— cell@20:: l1.seeking.releaseThe machine writes the inner doer into the Cell's own list of doers, waiting for the inner listener. Its action is local: it will release what it hears as the Cell's result.
Where it happens
registerDescriptorDefinition()Vol. 02 §4.2Stores a doer's description under its name, and lists it under every listener it waits for.
- Specification
- Vol. 02 §4.2
- Code
registerDescriptorDefinition()incore/registers/register-descriptor-definition.ts, line 19: the description is stored under its name- Journal
- #23 ·
BIND.DEFS · register-descriptor· id: cell@20::l1.seeking.release, interests: ["cell@20::l1.seeking.gate"] · by region:cell@20 - Picture
- doer cell@20::
l1.seeking.release: — → acts on cell@20::l1.seeking.gate; releases cell@20::knowledge.l1(release@1)
core/registers/register-descriptor-definition.ts· build 043cc8b// BIND.DEFS and DISPATCH write (Vol. 02 §4.2): the registration payload// lands as data; the dispatch table indexes the descriptor id under every// declared interest (the activation knot plus every demand for an operator// bind, the one subscription for an emit descriptor). Duplicate-id rejection// is the station's verdict (ADR-011 finding 3) — this op only records an// accepted registration.import type { DescriptorDefinedPayload } from "../topology/gate";import type { TopologyRegisters } from "./topology-registers";import type { RegisterFile } from "./register-file";import { recordTransition } from "./record-transition";export function registerDescriptorDefinition(file: RegisterFile,region: TopologyRegisters,payload: DescriptorDefinedPayload,interests: readonly string[]): void {region.bindDefs.set(payload.id, payload);↑ the description is stored under its namefor (const interest of interests) {const list = region.dispatch.get(interest);if (list) list.push(payload.id);else region.dispatch.set(interest, [payload.id]);↑ listed under the listener it waits for}recordTransition(file, `topology:${region.regionId}`, "BIND.DEFS", "register-descriptor", {↑ the change is written into the journalid: payload.id,interests});}
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 #23
133The membrane passes #23MEMBRANE.CURSOR · sweep
a wave is settlingengine: at the endmembrane: passing #23
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
- end of the log
The membrane What before after pointer — the next record to pass #23 #24 #23 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
- #23 ·
MEMBRANE.CURSOR · sweep· offset: 23 · by membrane - Picture
- pointer — the next record to pass: #23 → #24
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 doer's definition
Brings a doer into the machine: its name, the listener it acts on, what else it needs, and what it does once it may act — release a fact itself, ask the world for a fact, or ask the world for a whole Cell. The return doer is the simplest sort: it writes one fact when its listener is ready.
#23sys.descriptor.defined the machine
| envelope | |
|---|---|
offset | 23Its 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 | sys.descriptor.definedWhich of the four kinds of record the machine knows. The kind decides what the payload holds. |
key | ∅No lane (∅): a definition belongs to the whole machine, not to one lane. |
| payload | |
id | cell@20::l1.seeking.releaseThe doer's name, unique in the machine. |
| payload.operator | |
on | cell@20::l1.seeking.gateThe listener it acts on: when that listener is ready, the doer's lane becomes active. |
demands | ×0What else it needs before it may act — other listeners, and the name each one's understanding takes in its scope. It waits for all of them: a barrier. |
| payload.operator.service | |
instruction | «Release the seat's answer as knowledge.l1.»What it does, or asks the world to do, in words. |
action | release@1A local action chosen by name: the machine performs it itself, and nothing crosses the membrane. |
schema | typeThe shape the world's answer must have. |
| payload.operator.service.emit | |
writes | cell@20::knowledge.l1The type its result is written as. |
| payload | |
emittedBy | admit.note.gate--l1.seeking.planner#1The intention that wrote this definition — only what the machine wrote itself carries it. |
home | cellRef · localIdWhere it lives: the Cell, and its own name inside it. |
end · #23
In the specificationVol. 03 §1Vol. 03 §2Vol. 03 §5Vol. 04 §2.2Vol. 06 §2Vol. 06 §3Vol. 12 §3
Names it shares with other records
cell@20::l1.seeking.release— also on #30 the private resultadmit.note.gate--l1.seeking.planner#1— also on #19 a request: a Cell, #22 inner listener
The record as the machine keeps it
{
"offset": 23,
"kind": "sys.descriptor.defined",
"key": null,
"payload": {
"id": "cell@20::l1.seeking.release",
"operator": {
"on": "cell@20::l1.seeking.gate",
"demands": [],
"service": {
"instruction": "Release the seat's answer as knowledge.l1.",
"schema": {
"type": "object"
},
"emit": {
"writes": "cell@20::knowledge.l1"
},
"action": "release@1"
}
},
"emittedBy": "admit.note.gate--l1.seeking.planner#1",
"home": {
"cellRef": "cell@20",
"localId": "l1.seeking.release"
}
}
}