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.
1.8 KiB
1.8 KiB
name, description
| name | description |
|---|---|
| hal-new-issue | Use when something is wrong with the HAL mesh at the level of design or governance — a rule enforced by nothing, a stated behaviour that does not happen, a failure the design lets pass silently. Triggers on "this is broken", "open an issue", "that rule isn't enforced", "this reports success and does nothing". |
hal-new-issue
Opens a numbered issue. Authoritative playbook:
00-GENESIS/process/03-issues.md.
First, decide it belongs here
Belongs in 04-ISSUES |
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 |
| Finding the owner needs the whole mesh in view | Symptom → fix, once the answer is known |
Search the knowledge base first for the literal symptom text. If the answer is already there, this is not an issue — it is a lookup. If the answer is a general lesson, it belongs in both.
Steps
-
Next free number. Create
04-ISSUES/NNN-short-name/00-report.mdwith:--- status: open opened: YYYY-MM-DD located-in: [] fixed-by: amended-design: --- -
Write the symptom as observed, in plain terms, with the evidence that it happened — what was run, what came back, when.
-
Say why it matters beyond the instance. An issue that is only one occurrence is a knowledge base entry.
-
End with open questions rather than a proposed fix. Diagnosis is a separate step.
Do not
- Do not name nodes, domains, addresses or paths. This repository is public.
- Do not guess the owner —
located-in:is filled by diagnosis, not by opening.