Follow papa-hq's research convention; the mesh links nothing

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.
2026-08-23 09:29:09 +02:00
parent 702efca6bb
commit f05e4a0dce
17 changed files with 143 additions and 28 deletions
@@ -9,7 +9,7 @@ design. Also: an as-is document that raises a question nobody can answer.

 1. Take the next free number: highest `01-RESEARCH/NNN-*` plus one, zero-padded to three
   digits. Never skip or reuse a number.
-2. Create `01-RESEARCH/NNN-descriptive-name/` and a `status.md` in it carrying:
+2. Create `01-RESEARCH/NNN-descriptive-name/` and a `00-overview.md` in it carrying:

   ```yaml
   ---
@@ -22,7 +22,7 @@ design. Also: an as-is document that raises a question nobody can answer.
   Then a short prose summary: **what** is being investigated, **why**, and **what it
   touches**.
 3. Do the research in further documents in the same folder — notes, option analyses, evidence,
-   draft designs. Anything goes. Keep the summary in `status.md` current as the effort changes
+   draft designs. Anything goes. Keep the summary in `00-overview.md` current as the effort changes
   shape.

 ## What makes research worth reading
@@ -37,7 +37,7 @@ carries the whole lesson without naming anything.

 ## Do not

- Do not put status in prose. It lives in `status.md`'s frontmatter, and the prose must not restate it.
+- Do not put status in prose. It lives in `00-overview.md`'s frontmatter, and the prose must not restate it.
 - Do not set `became:` while the effort is open — playbook 02 sets it at closure.
 - Do not write into `02-DESIGN` from an open effort.

@@ -25,7 +25,7 @@
   ---
   ```

-4. **Close the effort.** Set the effort's `status.md` frontmatter to `status: graduated` and
+4. **Close the effort.** Set the effort's `00-overview.md` frontmatter to `status: graduated` and
   `became:` pointing at the design document and the decision record.
 5. **Add a ledger line.** Append the decision to [`DECISIONS.md`](../../DECISIONS.md) under
   today's heading, pointing at the record.