jschoubben
f05e4a0dce
Research efforts move from status.md to 00-overview.md with active / graduated / abandoned, matching papa-hq so the two repositories read the same way. Playbooks, skills, README and the ledger follow. Reverses yesterday's withdrawal of the symlink note in GENESIS. The note was right and the withdrawal was wrong: the intent is that the mesh creates no symlinks at all, so a founding document listing "symlinks, not copies" as a design principle does point the opposite way from where this is going, and that is a contradiction rather than a stale detail. ADR 0018 records the position, proposed. ADR 0011 stays as it is — it is the historical decision and the incident behind it is why anyone believes either record — and is superseded in intent, not edited. Its one editorial line, which called the wider reading false, is corrected to state what is actually true: centralising who may link narrowed the incident class without closing it, because a link the installer makes resolves exactly like one made by hand. The argument that kept linking was staleness. ADR 0004 removed it: every managed file is already derived and reconciled, so a copy is the natural form and a pointer into source is the shape the mesh's own model forbids everywhere else. What is not settled, and is marked open, is how staleness gets detected — which is the decision that makes or breaks it.
43 lines
1.6 KiB
Markdown
43 lines
1.6 KiB
Markdown
---
|
|
name: hal-new-research
|
|
description: 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`](../../../00-GENESIS/process/01-research.md) — read it;
|
|
this skill only does the mechanical setup.
|
|
|
|
## Steps
|
|
|
|
1. Find the next free number: list `01-RESEARCH/NNN-*`, take the highest plus one, zero-padded
|
|
to three digits.
|
|
2. Create `01-RESEARCH/NNN-descriptive-name/` (kebab-case from the topic).
|
|
3. Create `00-overview.md` in it with exactly this frontmatter, then a prose summary of **what** is
|
|
being investigated, **why**, and **what it touches**:
|
|
|
|
```yaml
|
|
---
|
|
status: active
|
|
initiated: YYYY-MM-DD
|
|
touches: []
|
|
became: []
|
|
---
|
|
```
|
|
|
|
4. 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-graduate` sets it at closure.
|
|
- Do not skip or reuse a sequence number.
|
|
- Do not write into `02-DESIGN` from 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.
|