Name ADR 0457 and ADR 0463 in design 47, and write the day's delivery lessons into playbook 07 #444

2026-10-20T18:00:18Z

mesh-tools commented

2026-10-20 18:00:18 +00:00

Design 47's catch-up of merges nobody heard is decided by ADR 0457 and bounded by ADR 0463 (issue 1336, delivered by mesh-controller #407 and #408), so the design's frontmatter names both.

Playbook 07 gains four lessons from 2026-10-20:

a failed plan's Retry is asked alone, never beside an Approve (issue 1408);
an ask is named to the operator only after it is read on the router;
a merge check's wait is read from its delivery (mesh-delivery.show), since the build queue never lists a running check;
a catalogue change that removes a module is judged by mesh-controller's unit suite against the catalogue's branch (MESH_CHECK_BESIDE), since a try reads the catalogue's main (issue 1406).

Checks run locally: records, index, cycle, words pass.

Reviewed-by: review-hq-47@shanks at 5705da30c0

Design 47's catch-up of merges nobody heard is decided by ADR 0457 and bounded by ADR 0463 (issue 1336, delivered by mesh-controller #407 and #408), so the design's frontmatter names both. Playbook 07 gains four lessons from 2026-10-20: - a failed plan's Retry is asked alone, never beside an Approve (issue 1408); - an ask is named to the operator only after it is read on the router; - a merge check's wait is read from its delivery (`mesh-delivery.show`), since the build queue never lists a running check; - a catalogue change that removes a module is judged by mesh-controller's unit suite against the catalogue's branch (`MESH_CHECK_BESIDE`), since a try reads the catalogue's main (issue 1406). Checks run locally: records, index, cycle, words pass. Reviewed-by: review-hq-47@shanks at 5705da30c006b436e43aaf60e4a2fb513acd6823

mesh-tools added 2 commits 2026-10-20 18:00:18 +00:00

Name ADR 0457 and ADR 0463 in design 47, and write the day's delivery lessons into playbook 07 1d7cfed47a

Design 47's catch-up of merges nobody heard is decided by ADR 0457 and bounded by ADR 0463, so other sessions read them from its frontmatter. Playbook 07 gains four lessons from 2026-10-20: a Retry is never asked beside an Approve (issue 1408), an ask is named only after it is read on the router, a check's wait is read from its delivery and not the build queue, and a catalogue change removing a module is tried against the controller (issue 1406).

Judge a catalogue removal by the controller's unit tests against the catalogue's branch, not by a try

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

Details

mesh/repo-check head 5705da30c006 merged into trunk a5c6c98ecca0 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

5705da30c0

A controller try reads the catalogue's main, so it would have passed for mesh-catalog #381 (review round 1).

mesh-tools commented

2026-10-20 18:00:27 +00:00

Delivery novox/hq@5705da30c006 — delivered since 2026-10-20T18:03:07Z

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

Transitions

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

2026-10-20 18:03:06 +00:00

mesh-tools deleted branch design/47-adr-0457-0463-and-lessons

2026-10-20 18:03:07 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#444