jochen ace8f6c398 Renumber the fixing-status record to ADR 0284 (issue 406) ...

hq #294 (issue 386) and #295 (issue 399) both merged a record numbered 0283;
#294 landed first and keeps it. The branch that lands last renumbers.

2026-10-10 21:35:34 +02:00

..

00-overview.md

An issue's status lives in the issue tracker: playbook 03, cycle.py and the notes slice 3 of ADR 0275 asked for

2026-10-10 15:54:32 +02:00

01-research.md

The numbering is the flow: decisions are 02, design is 03

2026-08-23 18:05:11 +02:00

02-graduation.md

Issue reports carry only opened: the tracker holds every status, so no copy can drift

2026-10-10 17:44:18 +02:00

03-issues.md

Renumber the fixing-status record to ADR 0284 (issue 406)

2026-10-10 21:35:34 +02:00

04-build-handoff.md

Issue 354: a decided rename was never scheduled, and a record that defers work names its issue

2026-10-09 19:27:05 +02:00

05-constitution-sync.md

ADR 0081: a decision nothing cites is not yet in the chain

2026-09-17 22:36:33 +02:00

06-writing-a-module.md

Graduate research 034: the mesh in domains, one word per thing, checked

2026-10-07 19:58:39 +02:00

07-feature-branches.md

Playbook 07: a feature worktree needs the siblings the lab reads

2026-09-21 00:27:01 +02:00