jschoubben
0760280bc6
Tool servers — 56 modules, over half — were written up as the biggest missing thing. They are expressible with what exists, and the first framing was wrong in a way worth keeping: a module provides `tools` and the session requires them does not work, because a requirement has one answer and 56 modules offering tools would be 56 answers. Turned around it fits exactly. The session provides `tool-host`; every module offering tools requires it and contributes where its tools are. Many-to-one is what `contributes` has always been, and the session receives all of them in one file. Verified by resolving it rather than by reading the code. It only became possible today: until 022, several modules on one node requiring the same thing was refused outright. Worth noting because it means the credential fix bought more than credentials. What remains is a decision about what a tool server is, which is work rather than a missing shape. The entry stays in the list rather than being deleted — a checklist that quietly loses its biggest item reads as though nobody looked.
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.