Files
hq/03-DESIGN
jschoubben 4baf34c7c3 Write milestone H's design lines so the one model is decided before code
Design 47 carried the commit-on-a-watched-branch model and the earlier
per-pull-request model side by side; the operator's answers of
2026-11-17 and 2026-11-20 (ADR 0682) lived only in lead answers. The
part H-1 to H-3 (design 47 H §734 to §765) states the merge call as the
start and group, the gate's watchdog, the take-in and validate step, one
pipeline per take-in with none in parallel, the want rule, the builder's
missing lines, reads made events, the missing read tools and what
retires; G's contradicting lines are corrected in place, the main file
gains the wake-up rule, tests 110 to 113 and the H row, and the
glossary gains merge call, untaken head, take-in and mover.

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 01:37:02 +01:00
..

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.