Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape #426

2026-10-18T19:26:14Z

mesh-tools commented

2026-10-18 19:26:14 +00:00

The lesson of design 47's release 1-2 (2026-10-18), written where the next prepare step reads it (playbook 07: 'when this playbook meets a problem, the lesson is added here').

The release was cut as one milestone, and its prepare step found three orders inside it: an SDK change still ships before its users; a new wire key between the controller and the node-engine needs a node that says it reads it; and the first module of a repository the catalogue never built registers only by the route the controller allows. A fourth, the watchman needing events only a system account hears and a bucket whose keys expire, needed decisions first (ADR 0431, ADR 0433). Each became a cut, said to the operator. And a fixture written from memory (a build key the controller never writes) let every test pass.

Two new items in step 0 (6 and 7); the old item 6 becomes 8, and no other playbook names it. A playbook edit of a few lines (playbook 08 step 4): the operator's Approve of its merge is its review. sh merge-check.sh passes.

Reviewed-by: operator's Approve (playbook 08 step 4) at 86e66dd51f

The lesson of design 47's release 1-2 (2026-10-18), written where the next prepare step reads it (playbook 07: 'when this playbook meets a problem, the lesson is added here'). The release was cut as one milestone, and its prepare step found three orders inside it: an SDK change still ships before its users; a new wire key between the controller and the node-engine needs a node that says it reads it; and the first module of a repository the catalogue never built registers only by the route the controller allows. A fourth, the watchman needing events only a system account hears and a bucket whose keys expire, needed decisions first (ADR 0431, ADR 0433). Each became a cut, said to the operator. And a fixture written from memory (a build key the controller never writes) let every test pass. Two new items in step 0 (6 and 7); the old item 6 becomes 8, and no other playbook names it. A playbook edit of a few lines (playbook 08 step 4): the operator's Approve of its merge is its review. `sh merge-check.sh` passes. Reviewed-by: operator's Approve (playbook 08 step 4) at 86e66dd51fcfd1dc76101a2045345536f20b9052

mesh-tools added 1 commit 2026-10-18 19:26:14 +00:00

Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape (design 47 release 1-2, 2026-10-18)

mesh/merge-gate head 86e66dd51fcf merged into trunk a353ed21c0a1 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 86e66dd51fcf merged into trunk a353ed21c0a1 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

86e66dd51f

mesh-tools commented

2026-10-18 19:26:22 +00:00

Delivery novox/hq@86e66dd51fcf — delivered since 2026-10-18T19:33:34Z

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

Transitions

2026-10-18 19:26 (new) → proposed (announced): novox/hq#426's head announced
2026-10-18 19:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 19:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 19:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 19:33 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@86e66dd51fcf` — **delivered** since 2026-10-18T19:33:34Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-18 19:26 (new) → proposed (announced): novox/hq#426's head announced - 2026-10-18 19:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 19:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 19:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 19:33 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 merged commit f7915f7f29 into main

2026-10-18 19:33:32 +00:00

mesh-tools deleted branch docs/prepare-checks-release-orders

2026-10-18 19:33:32 +00:00

mesh-tools referenced this pull request

2026-10-18 22:11:12 +00:00

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 #427

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#426