jschoubben ada703e790 Write a graduation's records side by side, from the confirmed direction (playbook 02) ...

Proposing records one after another serialises their reviews and the
operator's asks; retyping the effort's findings into each record makes them
long and gives the review more to send back.

2026-10-16 02:09:57 +02:00

..

00-overview.md

Make playbooks 01, 02 and 04 one cycle from idea to delivered milestones

2026-10-15 21:18:15 +02:00

01-research.md

Settle research decisions before proposing versions, and test on the cheapest bed (playbook 01)

2026-10-16 02:09:22 +02:00

02-graduation.md

Write a graduation's records side by side, from the confirmed direction (playbook 02)

2026-10-16 02:09:57 +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

Confirm milestones before opening their issues, name issue 845 for the check, keep 01's withdrawal and history lines

2026-10-15 21:19:01 +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

Show the report's issues as a tree, and keep the agent's brief, the red-check rule and the forge-commit check, in playbook 07

2026-10-15 19:52:48 +02:00

08-small-fixes.md

Let a small fix cover two or three related issues in one repository (playbook 08)

2026-10-15 22:37:12 +02:00