jschoubben 37a01b93a5 Use the glossary's word for the milestone's branch

2026-10-21 18:05:07 +02:00

..

00-overview.md

Keep the drawn overview of the playbooks in hq, for a later docs site

2026-10-19 13:27:55 +02:00

01-research.md

Playbooks 01 and 02: place research in the domains before its direction, and carry its words into the glossary at graduation (ADR 0244)

2026-10-16 12:38:59 +02:00

02-graduation.md

Playbook 02: wrap the check line and name the step it means (review round 1)

2026-10-18 17:05:46 +02:00

03-issues.md

Keep playbook 03's rule as it was, in plain words, and say how the record is searched (review of #318)

2026-10-11 21:07:32 +02:00

04-build-handoff.md

Design 47: release 1-2 is the six milestones R1a to R2c, each one release; playbook 04 splits a milestone that holds a release order (the operator, 2026-10-19)

2026-10-19 00:11:02 +02:00

05-constitution-sync.md

Say what the old 'knowledge base' meant, now that the word names the module (issue 430)

2026-10-11 20:54:15 +02:00

06-writing-a-module.md

Remove the decision records and research efforts, which the knowledge base now holds whole (issue 426)

2026-10-11 12:56:09 +02:00

07-feature-branches.md

Make a small fix in mesh-sdk or mesh-controller ride with the milestone's release, so each is delivered once per milestone

2026-10-21 18:04:49 +02:00

08-small-fixes.md

Use the glossary's word for the milestone's branch

2026-10-21 18:05:07 +02:00

09-cleanup.md

Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list

2026-10-16 20:51:00 +02:00

playbooks.html

Make a small fix in mesh-sdk or mesh-controller ride with the milestone's release, so each is delivered once per milestone

2026-10-21 18:04:49 +02:00