a wave is settlingengine working on #23membrane waiting at #20

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

Read as

when the engine took #23

  1. 127The engine takes #23ENGINE.CURSOR · propagate

    a wave is settlingengine: working on #23membrane: waiting at #20

    The log
    1. #0a listener
    2. #1a doer
    3. #2listener: the charter
    4. #3doer: the author
    5. #4listener: charter seen
    6. #5listener: blueprint seen
    7. #6doer: the planner
    8. #7listener: assess · charter
    9. #8listener: assess · result
    10. #9doer: the evaluator
    11. #10the charter wanted
    12. #11the blueprint
    13. #12readiness
    14. #13readiness
    15. #14a request: a charter
    16. #15the charter proposed
    17. #16the charter defined
    18. #17readiness
    19. #18readiness
    20. #19a request: a Cell
    21. #20the seedmembrane
    22. #21the Cell is open
    23. #22inner listener
    24. #23inner doerengine · working
    25. #24the Cell's context
    26. end of the log
    The engine
    Whatbeforeafter
    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.1

    The 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() in core/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
    1. // ENGINE.CURSOR advance (Vol. 02 §4.1) — the machine's instruction pointer:
    2. // returns the tuple at the cursor and moves it forward exactly once, or null
    3. // at quiescence. Advancing IS the context switch: the ambient wave context
    4. // moves to the propagated tuple in the same movement, so every transition
    5. // journalled during its propagation is attributed to it — the cube's spine.
    6. // The cursor never rewinds.
    7. import type { WaveTuple } from "../wave/gate";
    8. import type { RegisterFile } from "./register-file";
    9. import { recordTransition } from "./record-transition";
    10. import { setDriver, setWaveContext } from "./set-wave-context";
    11. export function takeNextTuple(file: RegisterFile): WaveTuple | null {
    12. const engine = file.registers.engine;
    13. if (engine.cursor >= engine.base + engine.window.length) return null;↑ at the end of the log, the engine stops
    14. const tuple = engine.window[engine.cursor - engine.base];
    15. engine.cursor += 1;↑ the engine's pointer moves on by one
    16. setWaveContext(file, { offset: tuple.offset, phase: "propagate" });
    17. setDriver(file, "engine");
    18. recordTransition(file, "engine", "ENGINE.CURSOR", "propagate", { offset: tuple.offset });↑ the change is written into the journal
    19. return tuple;
    20. }

    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)

  2. 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
    1. #0a listener
    2. #1a doer
    3. #2listener: the charter
    4. #3doer: the author
    5. #4listener: charter seen
    6. #5listener: blueprint seen
    7. #6doer: the planner
    8. #7listener: assess · charter
    9. #8listener: assess · result
    10. #9doer: the evaluator
    11. #10the charter wanted
    12. #11the blueprint
    13. #12readiness
    14. #13readiness
    15. #14a request: a charter
    16. #15the charter proposed
    17. #16the charter defined
    18. #17readiness
    19. #18readiness
    20. #19a request: a Cell
    21. #20the seedmembrane
    22. #21the Cell is open
    23. #22inner listener
    24. #23inner doerengine · working
    25. #24the Cell's context
    26. end of the log
    The figure of cell@20
    Whatbeforeafter
    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.gate is ready, it wakes—cell@20::l1.seeking.release

    The 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.2

    Stores a doer's description under its name, and lists it under every listener it waits for.

    Specification
    Vol. 02 §4.2
    Code
    registerDescriptorDefinition() in core/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
    1. // BIND.DEFS and DISPATCH write (Vol. 02 §4.2): the registration payload
    2. // lands as data; the dispatch table indexes the descriptor id under every
    3. // declared interest (the activation knot plus every demand for an operator
    4. // bind, the one subscription for an emit descriptor). Duplicate-id rejection
    5. // is the station's verdict (ADR-011 finding 3) — this op only records an
    6. // accepted registration.
    7. import type { DescriptorDefinedPayload } from "../topology/gate";
    8. import type { TopologyRegisters } from "./topology-registers";
    9. import type { RegisterFile } from "./register-file";
    10. import { recordTransition } from "./record-transition";
    11. export function registerDescriptorDefinition(
    12. file: RegisterFile,
    13. region: TopologyRegisters,
    14. payload: DescriptorDefinedPayload,
    15. interests: readonly string[]
    16. ): void {
    17. region.bindDefs.set(payload.id, payload);↑ the description is stored under its name
    18. for (const interest of interests) {
    19. const list = region.dispatch.get(interest);
    20. if (list) list.push(payload.id);
    21. else region.dispatch.set(interest, [payload.id]);↑ listed under the listener it waits for
    22. }
    23. recordTransition(file, `topology:${region.regionId}`, "BIND.DEFS", "register-descriptor", {↑ the change is written into the journal
    24. id: payload.id,
    25. interests
    26. });
    27. }

    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

  1. 133The membrane passes #23MEMBRANE.CURSOR · sweep

    a wave is settlingengine: at the endmembrane: passing #23

    The log
    1. #0a listener
    2. #1a doer
    3. #2listener: the charter
    4. #3doer: the author
    5. #4listener: charter seen
    6. #5listener: blueprint seen
    7. #6doer: the planner
    8. #7listener: assess · charter
    9. #8listener: assess · result
    10. #9doer: the evaluator
    11. #10the charter wanted
    12. #11the blueprint
    13. #12readiness
    14. #13readiness
    15. #14a request: a charter
    16. #15the charter proposed
    17. #16the charter defined
    18. #17readiness
    19. #18readiness
    20. #19a request: a Cell
    21. #20the seed
    22. #21the Cell is open
    23. #22inner listener
    24. #23inner doermembrane · passing
    25. #24the Cell's context
    26. end of the logengine
    The membrane
    Whatbeforeafter
    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 §3

    The 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() in core/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
    1. // MEMBRANE.CURSOR advance (Vol. 02 §4.6, Vol. 07 §3): the membrane's own
    2. // reading of the one log — the second reception of one publication, never a
    3. // second truth. The cursor advances exactly once per offset per machine:
    4. // the exactly-once discharge guarantee lives in this movement.
    5. import type { WaveTuple } from "../wave/gate";
    6. import type { RegisterFile } from "./register-file";
    7. import { recordTransition } from "./record-transition";
    8. import { setDriver, setWaveContext } from "./set-wave-context";
    9. export function sweepNextTuple(file: RegisterFile): WaveTuple | null {
    10. const engine = file.registers.engine;
    11. const membrane = file.registers.membrane;
    12. if (membrane.cursor >= engine.base + engine.window.length) return null;
    13. const tuple = engine.window[membrane.cursor - engine.base];
    14. membrane.cursor += 1;↑ the membrane's pointer moves on by one
    15. setWaveContext(file, { offset: tuple.offset, phase: "sweep" });
    16. setDriver(file, "membrane");
    17. recordTransition(file, "membrane", "MEMBRANE.CURSOR", "sweep", { offset: tuple.offset });↑ the change is written into the journal
    18. return tuple;
    19. }

    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
offset23Its 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.
kindsys.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
idcell@20::l1.seeking.releaseThe doer's name, unique in the machine.
payload.operator
oncell@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.
actionrelease@1A local action chosen by name: the machine performs it itself, and nothing crosses the membrane.
schematypeThe shape the world's answer must have.
payload.operator.service.emit
writescell@20::knowledge.l1The type its result is written as.
payload
emittedByadmit.note.gate--l1.seeking.planner#1The intention that wrote this definition — only what the machine wrote itself carries it.
homecellRef · 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

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"
  }
 }
}