jschoubben
702efca6bb
HQ held only the to-be. Every reader had to already know the system the decisions were about, and an as-is claim had nowhere to live except inside an intention. Adds 02-DESIGN/00-as-is — eleven documents written from the implementation and the operational record, not from intent, including the parts nobody would choose again. The two existing designs move under 01-to-be. Layers are declared in frontmatter and never mix: a design that ships does not move, its as-is counterpart is written, and both stand. Back-fills adr/0001-0014 for decisions taken in implementation and never recorded — the broker, the module abstraction, the mesh database, managed files, provisioning, migrations, the workspace removal, failing loudly, the constitution, application placement, linking, the employee model, the artifact, the three silos. Each marked reconstructed, dated from the history, and citing the evidence it was recovered from. The two existing records renumber to 0015 and 0016 so the ledger runs oldest first; 0017 extends 0015 to modules outside the core, principle only — the domain list is deliberately not invented here. how-we-build.md becomes the source of the mesh constitution, with a sync playbook, so the enforced copy stops being the only one that is true. Process becomes explicit: five playbooks, eight thin skills that defer to them, a repository map, and AGENTS.md with CLAUDE.md as its include. The five Observations become 04-ISSUES 001-005 where they can be owned and closed. 006 is new and uncomfortable: HQ is not indexed into the knowledge base. That claim is what decision 27 rests on, it was never checked, and the README now says so instead of repeating it. Also corrects the ADR index into something generated, the "02-DESIGN is empty" claim, the VISION.md pointer that did not survive the repo split, and a note asserting the symlink rule was contradicted — it was a misreading; the rule forbids hand-made links, the installer links by design.
47 lines
1.8 KiB
Markdown
47 lines
1.8 KiB
Markdown
# 04-ISSUES
|
|
|
|
The front door for "something is wrong" at the level of the mesh's design or governance.
|
|
Diagnosis happens here, where the whole mesh is in view; the fix lands in the owning code
|
|
repository.
|
|
|
|
## What belongs here
|
|
|
|
| Belongs here | Belongs in the knowledge base |
|
|
|---|---|
|
|
| The design permits a failure to be silent | How to fix one occurrence of it |
|
|
| A documented rule is enforced by nothing | A command that works around it |
|
|
| A stated invariant is false in practice | A node-specific quirk |
|
|
| The owner is unknown and finding it needs the whole mesh in view | Symptom → fix, once the answer is known |
|
|
|
|
The knowledge base already holds the operational record and is indexed on symptoms. **This
|
|
folder is not a second copy of it.** An issue here is a question HQ must *answer*; an entry
|
|
there is an incident someone must *clear*. An issue whose answer is a general lesson belongs in
|
|
both.
|
|
|
|
## Structure
|
|
|
|
```
|
|
NNN-short-name/
|
|
00-report.md the symptom as observed, with the evidence; status in frontmatter
|
|
01-diagnosis.md the investigation trail, dated, including what was ruled out
|
|
```
|
|
|
|
## Frontmatter, on `00-report.md`
|
|
|
|
```yaml
|
|
---
|
|
status: open | diagnosing | located | resolved | wontfix
|
|
opened: YYYY-MM-DD
|
|
located-in: [] # owning repo(s) or module(s), filled by diagnosis
|
|
fixed-by: # pull request or commit reference, filled at resolution
|
|
amended-design: # design doc path, when the root cause was a design gap
|
|
---
|
|
```
|
|
|
|
## Rules
|
|
|
|
- Anyone may open an issue. No localisation is required to report one.
|
|
- The full flow is playbook [`00-GENESIS/process/03-issues.md`](../00-GENESIS/process/03-issues.md).
|
|
- Closed issues are never deleted — they are the mesh's symptom-to-component memory.
|
|
- `wontfix` is legitimate and requires a sentence saying why.
|