CoAgnes Labthe study spaceresearch preview · build 1ececa2

a wave is settlingengine working on #36membrane waiting at #36

Wave 5 · Review and seal · record #36domain.factcell.reviewed

#36 · the decision

CellSpace seals the Cell and writes its seal (#37) and its export (#38).

Came froma personA person gave it at the door, after reading the assessment: the only thing a person adds in this wave. step 201

Read as

when it came in at the door

  1. 201Record #36 enters the logLOG · append

    a wave is settlingengine: next: #36membrane: waiting at #36

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionnewenginemembrane
    38. end of the log
    The log
    beforeafter
    records in the log3637
    #36—the decision · cell.reviewed

    The door adds the decision as #36: cell.reviewed, accept — who decided is stamped by the door, never typed.

    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
    LOG · append · offset: 36, kind: domain.fact · by engine
    Picture
    records in the log: 36 → 37
    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).
    7. import type { WaveEmission, WaveTuple } from "../wave/gate";
    8. import type { RegisterFile } from "./register-file";
    9. import { recordTransition } from "./record-transition";
    11. export function appendEmissions(file: RegisterFile, emissions: readonly WaveEmission[]): void {
    12. const engine = file.registers.engine;
    13. for (const emission of emissions) {
    14. const tuple: WaveTuple = { ...emission, offset: engine.base + engine.window.length };↑ the new record gets the next free number
    15. engine.window.push(tuple);↑ it is added at the end of the log
    16. recordTransition(file, "engine", "LOG", "append", {↑ the change is written into the journal
    17. offset: tuple.offset,
    18. kind: tuple.kind
    19. });
    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)

when the engine took #36

  1. 202The engine takes #36ENGINE.CURSOR · propagate

    a wave is settlingengine: working on #36membrane: waiting at #36

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionengine · workingmembrane
    38. end of the log
    The engine
    beforeafter
    pointer — the next record to take#36#37

    The engine's pointer moves past #36, the person's decision.

    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
    #36 · ENGINE.CURSOR · propagate · offset: 36 · by engine
    Picture
    pointer — the next record to take: #36 → #37
    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.
    8. import type { WaveTuple } from "../wave/gate";
    9. import type { RegisterFile } from "./register-file";
    10. import { recordTransition } from "./record-transition";
    11. import { setDriver, setWaveContext } from "./set-wave-context";
    13. export function takeNextTuple(file: RegisterFile): WaveTuple | null {
    14. const engine = file.registers.engine;
    15. if (engine.cursor >= engine.base + engine.window.length) return null;↑ at the end of the log, the engine stops
    16. const tuple = engine.window[engine.cursor - engine.base];
    17. engine.cursor += 1;↑ the engine's pointer moves on by one
    18. setWaveContext(file, { offset: tuple.offset, phase: "propagate" });
    19. setDriver(file, "engine");
    20. recordTransition(file, "engine", "ENGINE.CURSOR", "propagate", { offset: tuple.offset });↑ the change is written into the journal
    21. return tuple;
    22. }

    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. 203The Cell is sealedCELL.STATE · close-sealed

    a wave is settlingengine: working on #36membrane: waiting at #36

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionengine · workingmembrane
    38. end of the log
    cellspace/cell:cell@20
    beforeafter
    state“ready_for_review”“sealed”

    CellSpace acts on the decision at once: the Cell's state is closed as sealed, by the review at #36. Nothing inside it will move again.

    Where it happens closeCell()Vol. 12 §5.5 · Vol. 12 §8

    Closes a Cell for good — sealed, archived or failed. Nothing inside it moves again.

    Specification
    Vol. 12 §5.5 · Vol. 12 §8
    Code
    closeCell() in core/registers/close-cell.ts, line 16: the Cell's last state
    Journal
    #36 · CELL.STATE · close-sealed · reviewOffset: 36 · by cellspace
    Picture
    state: “ready_for_review” → “sealed”
    core/registers/close-cell.ts · build 043cc8b
    1. // Terminal Cell transitions (Vol. 12 §5.5, §8): `sealed` and `archived` are
    2. // committed human review outcomes; `failed` is the effect policy's one
    3. // honest closure. Only the first valid terminal stands — the station guards
    4. // the preconditions, this op is the movement.
    6. import type { CellRegisters } from "./cell-registers";
    7. import type { RegisterFile } from "./register-file";
    8. import { recordTransition } from "./record-transition";
    10. export function closeCell(
    11. file: RegisterFile,
    12. cell: CellRegisters,
    13. terminal: "sealed" | "archived" | "failed",
    14. detail?: unknown
    15. ): void {
    16. cell.state = terminal;↑ the Cell's last state
    17. recordTransition(file, `cellspace/cell:${cell.cellRef}`, "CELL.STATE", `close-${terminal}`, detail);↑ the change is written into the journal
    18. }

    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. 204The seal enters the log as #37LOG · append

    a wave is settlingengine: working on #36membrane: waiting at #36

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionengine · workingmembrane
    38. #37the Cell sealednew
    39. end of the log
    The log
    beforeafter
    records in the log3738
    #37—the Cell sealed · cell.sealed

    The public mark of the closing, cell.sealed, naming the assessment and the review it rests on, is written as #37.

    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
    #36 · LOG · append · offset: 37, kind: domain.fact · by engine
    Picture
    records in the log: 37 → 38
    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).
    7. import type { WaveEmission, WaveTuple } from "../wave/gate";
    8. import type { RegisterFile } from "./register-file";
    9. import { recordTransition } from "./record-transition";
    11. export function appendEmissions(file: RegisterFile, emissions: readonly WaveEmission[]): void {
    12. const engine = file.registers.engine;
    13. for (const emission of emissions) {
    14. const tuple: WaveTuple = { ...emission, offset: engine.base + engine.window.length };↑ the new record gets the next free number
    15. engine.window.push(tuple);↑ it is added at the end of the log
    16. recordTransition(file, "engine", "LOG", "append", {↑ the change is written into the journal
    17. offset: tuple.offset,
    18. kind: tuple.kind
    19. });
    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)

  4. 205The export enters the log as #38LOG · append

    a wave is settlingengine: working on #36membrane: waiting at #36

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionengine · workingmembrane
    38. #37the Cell sealed
    39. #38the exportnew
    40. end of the log
    The log
    beforeafter
    records in the log3839
    #38—the export · knowledge.l1.accepted

    Then the export, #38: the Cell's result, now trusted, as knowledge.l1.accepted — with the charter, the assessment and the review it rests on. The only fact of the Cell root may act on.

    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
    #36 · LOG · append · offset: 38, kind: domain.fact · by engine
    Picture
    records in the log: 38 → 39
    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).
    7. import type { WaveEmission, WaveTuple } from "../wave/gate";
    8. import type { RegisterFile } from "./register-file";
    9. import { recordTransition } from "./record-transition";
    11. export function appendEmissions(file: RegisterFile, emissions: readonly WaveEmission[]): void {
    12. const engine = file.registers.engine;
    13. for (const emission of emissions) {
    14. const tuple: WaveTuple = { ...emission, offset: engine.base + engine.window.length };↑ the new record gets the next free number
    15. engine.window.push(tuple);↑ it is added at the end of the log
    16. recordTransition(file, "engine", "LOG", "append", {↑ the change is written into the journal
    17. offset: tuple.offset,
    18. kind: tuple.kind
    19. });
    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)

when the membrane passed #36

  1. 214The membrane passes #36MEMBRANE.CURSOR · sweep

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

    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 result
    32. #31the result, marked
    33. #32readiness
    34. #33a request: assess
    35. #34assessment proposed
    36. #35the Cell assessed
    37. #36the decisionmembrane · passing
    38. #37the Cell sealed
    39. #38the export
    40. #39readiness
    41. #40a request: present again
    42. end of the logengine
    The membrane
    beforeafter
    pointer — the next record to pass#36#37

    #36 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
    #36 · MEMBRANE.CURSOR · sweep · offset: 36 · by membrane
    Picture
    pointer — the next record to pass: #36 → #37
    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.
    6. import type { WaveTuple } from "../wave/gate";
    7. import type { RegisterFile } from "./register-file";
    8. import { recordTransition } from "./record-transition";
    9. import { setDriver, setWaveContext } from "./set-wave-context";
    11. export function sweepNextTuple(file: RegisterFile): WaveTuple | null {
    12. const engine = file.registers.engine;
    13. const membrane = file.registers.membrane;
    14. if (membrane.cursor >= engine.base + engine.window.length) return null;
    15. const tuple = engine.window[membrane.cursor - engine.base];
    16. membrane.cursor += 1;↑ the membrane's pointer moves on by one
    17. setWaveContext(file, { offset: tuple.offset, phase: "sweep" });
    18. setDriver(file, "membrane");
    19. recordTransition(file, "membrane", "MEMBRANE.CURSOR", "sweep", { offset: tuple.offset });↑ the change is written into the journal
    20. return tuple;
    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 6730f58 (2026-09-13)

Choose a step in the stack — or press →.

A fact: the person's decision

A person's judgement, committed like any other fact — accept, revise or archive. The machine acts on it exactly once.

#36domain.factcell.reviewed a person

envelope
offset36Its 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.reviewedThe fact type — cell.reviewed.
payload.data
cellRefcell@20The Cell reviewed.
decisionacceptAccept: the Cell is sealed and its result becomes an export.
actorauthorWho decided — stamped by the door, never typed.

end · #36

In the specificationVol. 03 §1Vol. 03 §5Vol. 07 §6Vol. 12 §5.5

Names it shares with other records

The record as the machine keeps it
{
 "offset": 36,
 "kind": "domain.fact",
 "key": "fragment-one-cell",
 "payload": {
  "factType": "cell.reviewed",
  "data": {
   "cellRef": "cell@20",
   "decision": "accept",
   "actor": "author"
  }
 }
}