mesh-adminandClaude Opus 5.5 c2d5323dea Say how several agents work one feature on one branch ...

Feature 57 was first worked as a pull request per issue into protected
branches and lost most of a day waiting on merge checks. Record the issue
as the unit, a review and checks once at the end, landing by fast-forward
under a lock, and the lessons met on the way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-14 19:50:14 +00:00

..

00-overview.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

01-research.md

Name the commit the knowledge base's records now come from, and link research with touches and decisions with rests-on (review of #312)

2026-10-11 13:25:21 +02:00

02-graduation.md

Name the commit the knowledge base's records now come from, and link research with touches and decisions with rests-on (review of #312)

2026-10-11 13:25:21 +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

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

2026-10-11 12:56:09 +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

Say how several agents work one feature on one branch

2026-10-14 19:50:14 +00:00