Playbooks 01, 02 and 04: one cycle from idea to delivered milestones #366

2026-10-15T19:19:09Z

mesh-tools commented

2026-10-15 19:19:09 +00:00

The operator, 2026-10-15: playbook 04 was odd (straight from a settled design to building, no work breakdown, and it contradicted 07 on pull requests), and 01 and 02 should be revised with it.

01 Research starts from the operator's idea in either form (a new idea, or one for an existing application; a bug goes to 03): read what is known, ask the operator a few setup questions one at a time with a recommendation, propose the effort (overview, questions, method), research with findings in 04-findings.md, then a direction in 05-direction.md the operator confirms. Bounds and a model per step; reporting as 07. Until issue 844 is delivered, findings go into an accepted active effort as dated insights.
02 Graduation graduates the confirmed direction, one decision record per choice that could be reversed on its own, at most three review rounds, then hands the design to 04.
04 Work breakdown and handoff (was Build handoff): milestones usable on their own (one-sentence outcome each), confirmed by the operator, then one issue per repository part linked by depends-on; each milestone is one feature step of 07, the next starting when the previous one's delivery plan is done. The rules that contradicted 07 are gone; how building is done is 07's. Its milestones check is tracked by issue 845.
The overview's table follows.

sh merge-check.sh passes. Reviewed independently before push: APPROVE at 0d66edb (round 1); its three non-blocking points are applied in 99243ec (milestones confirmed before issues are opened, issue 845 named, 01's withdrawal and history lines kept).

The operator, 2026-10-15: playbook 04 was odd (straight from a settled design to building, no work breakdown, and it contradicted 07 on pull requests), and 01 and 02 should be revised with it. - **01 Research** starts from the operator's idea in either form (a new idea, or one for an existing application; a bug goes to 03): read what is known, ask the operator a few setup questions one at a time with a recommendation, propose the effort (overview, questions, method), research with findings in `04-findings.md`, then a direction in `05-direction.md` the operator confirms. Bounds and a model per step; reporting as 07. Until issue 844 is delivered, findings go into an accepted active effort as dated insights. - **02 Graduation** graduates the confirmed direction, one decision record per choice that could be reversed on its own, at most three review rounds, then hands the design to 04. - **04 Work breakdown and handoff** (was Build handoff): milestones usable on their own (one-sentence outcome each), confirmed by the operator, then one issue per repository part linked by `depends-on`; each milestone is one feature step of 07, the next starting when the previous one's delivery plan is done. The rules that contradicted 07 are gone; how building is done is 07's. Its milestones check is tracked by issue 845. - The overview's table follows. `sh merge-check.sh` passes. Reviewed independently before push: APPROVE at 0d66edb (round 1); its three non-blocking points are applied in 99243ec (milestones confirmed before issues are opened, issue 845 named, 01's withdrawal and history lines kept).

mesh-tools added 2 commits 2026-10-15 19:19:10 +00:00

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

The operator found 04 odd on 2026-10-15: it went from a settled design straight to building,
with no work breakdown, and contradicted playbook 07 on pull requests. 01 now starts from the
operator's idea with setup questions, findings and a direction the operator confirms; 02
graduates that direction into one record per reversible choice and hands the design on; 04
breaks it into milestones usable on their own, one issue per repository part, each milestone
one feature step of 07. 01 notes the knowledge base's insight-only rule for an active effort
until issue 844 is delivered.

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

mesh/merge-gate head 99243ec47efa merged into trunk 5ff97ec3aa02 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 99243ec47efa merged into trunk 5ff97ec3aa02 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

99243ec47e

mesh-tools commented

2026-10-15 19:19:16 +00:00

Delivery novox/hq@99243ec47efa — delivered since 2026-10-15T19:23:09Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-15 19:19 (new) → proposed (announced): novox/hq#366's head announced
2026-10-15 19:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-15 19:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-15 19:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-15 19:23 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@99243ec47efa` — **delivered** since 2026-10-15T19:23:09Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-15 19:19 (new) → proposed (announced): novox/hq#366's head announced - 2026-10-15 19:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 19:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-15 19:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-15 19:23 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools added the mesh/ready label 2026-10-15 19:22:17 +00:00

mesh-tools commented

2026-10-15 19:22:17 +00:00

ready at 99243ec47e (the operator's word, 2026-10-15; independent review APPROVE at 0d66edb, its non-blocking points applied in this head).

ready at 99243ec47efadda30c6495252c260dfba430e197 (the operator's word, 2026-10-15; independent review APPROVE at 0d66edb, its non-blocking points applied in this head).

mesh-tools merged commit 046bbd3b30 into main

2026-10-15 19:23:09 +00:00

mesh-tools deleted branch playbooks/01-02-04-the-cycle

2026-10-15 19:23:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#366