jschoubben
fbf5b1d04b
Settles the question 15 left open: the mesh session holds its own memory in the mesh root, rather than assembling a view over the node sessions. Memory follows the rule the rest of the design already uses — the context root is the whole of what makes one session a different agent, and memory is part of what makes it that agent. The control-plane node is what makes this load-bearing rather than tidy. Two sessions share that machine; if memory belonged to the machine instead of the root they would share it too, and the mesh's recollection would be indistinguishable from that node's own — the collision 0026 exists to avoid, arriving through the back door. Also corrects an error made writing it up: memory is NOT declared state. The engram and tools are — the mesh says what they are and the host writes them (0011). Memory is written by the session itself and declared by nobody, so a mechanism that regenerates the root wholesale would erase it on the next heartbeat, silently, while reporting success. The root is not uniformly managed and which parts are has to be explicit.
03-DESIGN
The authoritative specification. Implementation is built against what is written here.
Two layers
| Folder | What it is |
|---|---|
00-as-is/ |
The mesh that exists today. Shipped behaviour, described as it is — including behaviour nobody would choose again. |
01-to-be/ |
The mesh being built toward. Every statement traceable to a record in 02-DECISIONS/. |
They are never mixed. A statement about the future does not belong in an as-is document, and an as-is document is never edited to describe an intention.
When a to-be design ships, it does not move. Its as-is counterpart is written or updated,
the to-be document's status becomes implemented, and both stand — one describing what runs,
the other recording what was intended. Deleting the intention loses the reasoning, which is
the expensive half.
Frontmatter
Every design document (not the READMEs) carries:
---
layer: as-is | to-be
status: designed | in-progress | implemented | abandoned
code: [] # owning code repo(s), from 00-META/repos.md
updated: YYYY-MM-DD # date of the last status change, not of text edits
decisions: [] # 02-DECISIONS/ records this document rests on
---
For an as-is document, status: implemented is the normal state — it describes something that
runs — and code: names where that implementation lives.
Status changes when implementation state changes, never because design text was edited. An
implemented claim must be defensible from the owning repository's main branch, not from
intent. If it cannot be checked, it is in-progress.
Cross-cutting views are generated from this frontmatter by the hq-status skill and never
written to disk.
What belongs here
Functional analysis, architectural description, and specification — prose and diagrams
only, no code. A manifest field may be named; a manifest may not be pasted. A document
enters the to-be layer only after the decision behind it is recorded in 02-DECISIONS/
and the research that produced it is closed.
Subfolders are encouraged where a layer grows enough to need them.