jschoubben
ecfc2c215e
The conversion's detail is operational and names machines, so it lives in the mesh's knowledge base rather than in this repository: `migration/where-service-data-lives` for where every service's data actually sits, and `troubleshooting/db-password-frozen-at-first-init` for the lockout. This document says the rule; those say the specifics. The lockout is the finding worth carrying here, because it is worse than the one this plan was already guarding against and it is likelier. A database image consumes its password variable only when its data directory is empty. Everything keeps data on a persistent directory, so the role holds whatever password it was created with for ever; regenerate the variable and the application moves on while the database does not, permanently, because nothing reconciles it. Eight modules are in that state today and work only because nobody has regenerated their credential since their data directory was created. It was already documented in the knowledge base and my survey had missed it — found by searching, which is the argument for the knowledge base existing.
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.