jschoubben
e99094ab94
Research 085 found that each acting part handled a change to itself by a case of its own, and that parts disagreed on the state they read: 7 of 24 failures since 2026-11-01. Design 47 now describes the catalog graph and the computed assignment graph kept per revision, a change delivered as its graph difference, acting parts' rules on their seats as bounded waits, the check on the change's own acting parts, the revision view, the gate's delivery record and the trace's links, with the bootstrap delivery before that milestone. It also settles what the records leave to this amendment, as proposals for the review: the acting rule's fields and mesh-sdk cost, the fingerprint handover, the build seat's ask that runs a program in the sandbox, the first tier's bound, the step events' subjects, and the tools the seams review listed. The glossary gains the seven words of research 085's Domains. The watcher's definition learns that a quiet five minutes is no reason to end, since its final report is its only channel. Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
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.