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.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| hal-new-research | Use when starting a new research effort in hal-hq — an idea, technology or approach worth investigating before it is committed to design. Triggers on "research X", "investigate X", "spike X", "should we use X", "is X worth doing". |
hal-new-research
Scaffolds a new research effort. Authoritative playbook:
00-GENESIS/process/01-research.md — read it;
this skill only does the mechanical setup.
Steps
-
Find the next free number: list
01-RESEARCH/NNN-*, take the highest plus one, zero-padded to three digits. -
Create
01-RESEARCH/NNN-descriptive-name/(kebab-case from the topic). -
Create
status.mdin it with exactly this frontmatter, then a prose summary of what is being investigated, why, and what it touches:--- status: ongoing initiated: YYYY-MM-DD touches: [] became: [] --- -
Do the research in further documents in the same folder. Keep the summary current.
Do not
- Do not restate the status in prose. It lives in frontmatter, in one place.
- Do not fill
became:while the effort is open —hal-graduatesets it at closure. - Do not skip or reuse a sequence number.
- Do not write into
02-DESIGNfrom an open effort. - Do not name the mesh being observed. Evidence is required; identification is forbidden.
Closing
An effort never just stops. It closes through hal-graduate as graduated or abandoned,
always with became: pointing at what it turned into. Nothing is deleted.