jschoubben e1987b3654 Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks (issue 1042) ...

The operator asked why review takes so long: a fresh reviewer per round or per mark reads
everything again, and a reviewer waiting on the forge's checks spends its run waiting.

2026-10-17 18:26:06 +02:00

..

00-overview.md

Playbook 09 and the hq-cleanup skill: a cleanup reads first, deletes only what the operator approves, and reports what it kept (the operator, 2026-10-16)

2026-10-16 20:01:13 +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: one design per thing; a graduation rewrites the design that covers it instead of writing a second (the operator, 2026-10-16)

2026-10-16 19:40:48 +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

Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)

2026-10-17 13:47:37 +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

Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks (issue 1042)

2026-10-17 18:26:06 +02:00

08-small-fixes.md

Playbook 08: check that the clone stays on main (issue 1010, review round 1)

2026-10-17 13:37:09 +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