jschoubben
cb1b055b80
The review by architectural domain found that readers of the seat list would name the indexer, never hear a removal, could deadlock a full restart, and that any folder could define a seat again; the-private-network's holder sat in mesh-sdk. ADR 0636 and the lead's rulings answer these, and the designs must say so before develop. - design 26: the seat list through a verb and two events of mesh-catalog; a reader without it acts on nothing new; a seat defined only in its domain's contracts module; states are any holder's, caller-written only for events and logs, each with its size cap, declared in the holder's requires; the renames move no state; the group's check reads every member's head; Connectivity in the mesh-networking repository, held by mesh-wireguard; acceptance tests by level and repository; two stale table rows corrected - design 47: the composer in mesh-delivery-sdk, the bus composer's seat parts in the grants part, placement's contract and check by their seat - design 20: a module's own package is fingerprinted by its own files - glossary: mesh-placement retired for tool descriptions too; the composition renamed to mesh-delivery-sdk's; six seats given their domains Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
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 decision record in the knowledge base (ADR 0290). |
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: [] # the decision records this document rests on, each "ADR NNNN"
---
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 the knowledge base and the research that produced it is closed.
Subfolders are encouraged where a layer grows enough to need them.