a wave is settlingengine working on #30membrane waiting at #28

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

Read as

when the engine took #30

  1. 168The engine takes #30ENGINE.CURSOR · propagate

    a wave is settlingengine: working on #30membrane: waiting at #28

    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 doer
    25. #24the Cell's context
    26. #25return listener
    27. #26return doer
    28. #27the return address
    29. #28the person's wordsmembrane
    30. #29readiness
    31. #30the private resultengine · working
    32. end of the log
    The engine
    Whatbeforeafter
    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.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
    #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
    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. 169CellSpace records the Cell's resultCELL.STATE,CELL.RESULT · record-result

    a wave is settlingengine: working on #30membrane: waiting at #28

    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 doer
    25. #24the Cell's context
    26. #25return listener
    27. #26return doer
    28. #27the return address
    29. #28the person's wordsmembrane
    30. #29readiness
    31. #30the private resultengine · working
    32. end of the log
    cellspace/cell:cell@20
    Whatbeforeafter
    state“running”“awaiting_assessment”
    resultValuenonetext = “A Cell is a bounded study the machine opens when a slot needs more th…”
    localResultOffsetnone30
    resultOffsetnone30

    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.3

    Records a Cell's result and moves the Cell to awaiting assessment: made, not yet trusted.

    Specification
    Vol. 12 §5.3
    Code
    recordCellResult() in core/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
    1. // The result transition (Vol. 12 §5.3): the declared producer's delegated
    2. // publication moves the Cell from `running` to `awaiting_assessment` with
    3. // the result fields in one movement — runtime success, distinct from
    4. // assessment and from human usefulness (the four verdicts never collapse).
    5. import type { CellRegisters } from "./cell-registers";
    6. import type { RegisterFile } from "./register-file";
    7. import { recordTransition } from "./record-transition";
    8. export function recordCellResult(
    9. file: RegisterFile,
    10. cell: CellRegisters,
    11. result: { offset: number; value: unknown }
    12. ): void {
    13. cell.state = "awaiting_assessment";↑ the Cell now awaits its assessment
    14. cell.localResultOffset = result.offset;
    15. cell.resultValue = result.value;
    16. cell.resultOffset = result.offset;↑ where its result stands in the log
    17. recordTransition(file, `cellspace/cell:${cell.cellRef}`, "CELL.STATE,CELL.RESULT", "record-result", {↑ the change is written into the journal
    18. state: cell.state,
    19. resultOffset: result.offset
    20. });
    21. }

    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)

  3. 170The result's public mark enters as #31LOG · append

    a wave is settlingengine: working on #30membrane: waiting at #28

    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 doer
    25. #24the Cell's context
    26. #25return listener
    27. #26return doer
    28. #27the return address
    29. #28the person's wordsmembrane
    30. #29readiness
    31. #30the private resultengine · working
    32. #31the result, markednew
    33. end of the log
    The log
    Whatbeforeafter
    records in the log3132
    #31—the result, marked · cell.result

    CellSpace 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 §1

    The 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() in core/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
    1. // The one LOG writer (Vol. 02 §4.1, Vol. 03 §1): emissions become tuples by
    2. // receiving the next dense absolute offset — `base + window.length` — and
    3. // nothing else ever grows the log. Each append is journalled under the
    4. // ambient context, so a batch born of a propagated tuple carries that
    5. // tuple's offset as its cause — the cube's provenance line (ADR-002).
    6. import type { WaveEmission, WaveTuple } from "../wave/gate";
    7. import type { RegisterFile } from "./register-file";
    8. import { recordTransition } from "./record-transition";
    9. export function appendEmissions(file: RegisterFile, emissions: readonly WaveEmission[]): void {
    10. const engine = file.registers.engine;
    11. for (const emission of emissions) {
    12. const tuple: WaveTuple = { ...emission, offset: engine.base + engine.window.length };↑ the new record gets the next free number
    13. engine.window.push(tuple);↑ it is added at the end of the log
    14. recordTransition(file, "engine", "LOG", "append", {↑ the change is written into the journal
    15. offset: tuple.offset,
    16. kind: tuple.kind
    17. });
    18. }
    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 f36e70d (2026-08-18)

when the membrane passed #30

  1. 185The membrane passes #30MEMBRANE.CURSOR · sweep

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

    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 doer
    25. #24the Cell's context
    26. #25return listener
    27. #26return doer
    28. #27the return address
    29. #28the person's words
    30. #29readiness
    31. #30the private resultmembrane · passing
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. end of the logengine
    The membrane
    Whatbeforeafter
    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 §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
    #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
    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 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
offset30Its 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.
kinddomain.factWhich of the four kinds of record the machine knows. The kind decides what the payload holds.
keyfragment-one-cellThis session's lane.
payload
factTypecell@20::knowledge.l1The private type: the Cell's name before the result's type.
payload.data
bindIdcell@20::l1.seeking.releaseThe inner doer.
uidcell@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

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