#15 · the charter is proposed

1. 84The engine takes #15ENGINE.CURSOR · propagate

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

   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 proposedengine · workingmembrane
   17. ·end of the log

   What	before		after
   pointer — the next record to take	#15	→	#16

   The engine moves on to #15 — the charter, as the world proposed it.

   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

   #15 · ENGINE.CURSOR · propagate · offset: 15 · by engine

   Picture

   pointer — the next record to take: #15 → #16

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

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

   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 proposedengine · workingmembrane
   17. ·end of the log

   No register changed its value.

   The answer carries the author's intention name, so CellSpace closes the request it indexed at #14. A second answer under the same name would find nothing to close.

   Where it happens consumeCausalRequest()Vol. 12 §5.1

   Closes a request once its answer has come: the index entry is spent, and a second answer under the same name finds nothing to close.

   Specification

   Vol. 12 §5.1

   Code

   consumeCausalRequest() in core/registers/consume-causal-request.ts, line 10: the request is marked as answered

   Journal

   #15 · REQUESTS · consume-request · uid: admit.note.gate--l1.seeking.charter.author#1 · by cellspace

   Picture

   no register changed its value

   1. 1// REQUESTS consumption (Vol. 12 §5.1): the first proposal or failure over a
   2. 2// causal request is terminal for it — a correlation spends exactly once,
   3. 3// even when what it bought was a rejection.
   4. 4
   5. 5import type { CausalRequest } from "../cells/gate";
   6. 6import type { RegisterFile } from "./register-file";
   7. 7import { recordTransition } from "./record-transition";
   8. 8
   9. 9export function consumeCausalRequest(file: RegisterFile, request: CausalRequest): void {
   10. 10 request.consumed = true;↑ the request is marked as answered
   11. 11 recordTransition(file, "cellspace", "REQUESTS", "consume-request", { uid: request.uid });↑ the change is written into the journal
   12. 12}

   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. 86The charter is defined as charter@15CHARTERS · define-charter

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

   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 proposedengine · workingmembrane
   17. ·end of the log

   What	before		after
   charters	empty	→	charter@15

   CellSpace fixes the proposed charter under a reference — charter@15, the proposal's place in the log — with a digest of its value. Everything of the Cell will name it; it is never edited.

   Where it happens defineCharter()Vol. 12 §5.1

   Fixes a proposed charter under its reference — the one place a charter is written; it is never edited.

   Specification

   Vol. 12 §5.1

   Code

   defineCharter() in core/registers/define-charter.ts, line 11: the charter is kept under its reference

   Journal

   #15 · CHARTERS · define-charter · ref: charter@15 · by cellspace

   Picture

   charters: empty → charter@15

   1. 1// CHARTERS write (Vol. 12 §5.1): a validated proposal becomes the canonical
   2. 2// Charter definition under its committed ref — never model-supplied, never
   3. 3// mutated; a replacement Charter is a new committed identity.
   4. 4
   5. 5import type { CharterRecord } from "../cells/gate";
   6. 6import type { RegisterFile } from "./register-file";
   7. 7import { cellsRegion } from "./cells-region";
   8. 8import { recordTransition } from "./record-transition";
   9. 9
   10. 10export function defineCharter(file: RegisterFile, record: CharterRecord): void {
   11. 11 cellsRegion(file).charters.set(record.ref, record);↑ the charter is kept under its reference
   12. 12 recordTransition(file, "cellspace", "CHARTERS", "define-charter", { ref: record.ref });↑ the change is written into the journal
   13. 13}

   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. 87The definition enters the log as #16LOG · append

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

   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 proposedengine · workingmembrane
   17. #16the charter definednew
   18. ·end of the log

   What	before		after
   records in the log	16	→	17
   #16	—	→	the charter defined · charter.defined

   The public mark that a charter now exists — charter.defined, with its reference and digest — is written as #16. Two listeners of the admission figure will hear it.

   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

   #15 · LOG · append · offset: 16, kind: domain.fact · by engine

   Picture

   records in the log: 16 → 17

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

1. 108The membrane passes #15MEMBRANE.CURSOR · sweep

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

   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 proposedmembrane · passing
   17. #16the charter defined
   18. #17readiness
   19. #18readiness
   20. #19a request: a Cell
   21. ·end of the logengine

   What	before		after
   pointer — the next record to pass	#15	→	#16

   #15 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

   #15 · MEMBRANE.CURSOR · sweep · offset: 15 · by membrane

   Picture

   pointer — the next record to pass: #15 → #16

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