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

2026-10-18T22:11:12Z

mesh-tools commented

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

The operator, 2026-10-19 00:10: a milestone is one release. Release 1-2 was confirmed as one milestone, and its prepare step found the release orders inside it (an SDK change before its users, a new wire key before the node that reads it, a new repository's first module, the decisions the watchman needed); each part then shipped as a release of its own, which the session called 'cuts', a word that is in no glossary.

Design 47: the R1-2 row becomes the six milestones R1a to R2c, each with its outcome, its acceptance tests and its issues (no state copied from the tracker); the paragraph says why; decisions += ADR 0433, 0434, 0435 (accepted).
Playbook 04: the release-order check names the orders to look for (as playbook 07 step 0 item 6, merged in #426), says a milestone cut by one may be usable only by the next and says so, and that a milestone found holding one is split into milestones in the design, never carried as parts.

A design and 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 d10965a341

The operator, 2026-10-19 00:10: a milestone is one release. Release 1-2 was confirmed as one milestone, and its prepare step found the release orders inside it (an SDK change before its users, a new wire key before the node that reads it, a new repository's first module, the decisions the watchman needed); each part then shipped as a release of its own, which the session called 'cuts', a word that is in no glossary. - Design 47: the R1-2 row becomes the six milestones R1a to R2c, each with its outcome, its acceptance tests and its issues (no state copied from the tracker); the paragraph says why; decisions += ADR 0433, 0434, 0435 (accepted). - Playbook 04: the release-order check names the orders to look for (as playbook 07 step 0 item 6, merged in #426), says a milestone cut by one may be usable only by the next and says so, and that a milestone found holding one is split into milestones in the design, never carried as parts. A design and 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 d10965a3414843336a4ed054b5233dee79bf6b91

mesh-tools added 1 commit 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 (the operator, 2026-10-19)

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

Details

mesh/repo-check head d10965a34148 merged into trunk f7915f7f2952 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

d10965a341

mesh-tools commented

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

Delivery novox/hq@d10965a34148 — delivered since 2026-10-18T22:17:19Z

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

Transitions

2026-10-18 22:11 (new) → proposed (announced): novox/hq#427's head announced
2026-10-18 22:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 22:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 22:17 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 22:17 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@d10965a34148` — **delivered** since 2026-10-18T22:17:19Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-18 22:11 (new) → proposed (announced): novox/hq#427's head announced - 2026-10-18 22:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 22:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 22:17 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 22:17 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 f9139feb30 into main

2026-10-18 22:17:17 +00:00

mesh-tools deleted branch docs/design-47-milestones-r1a-r2c

2026-10-18 22:17:18 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#427