ADR 0360 (accepted 2026-10-14) sends a merge's builds to every machine at once, with no first-machine gate. Design 57 assumed that gate in two places:
What a release costs: a fault on the release's first node held the release. Now the lab rehearsal is the only check before release 57 reaches every node; a failed apply or a failed prov.applied is named in the walk's end, raises apply-failing and is fixed forward.
P6 (issue 672): the gate counted a provisioned module healthy only after prov.applied (gateFacts). ADR 0362 (proposed) moves that wait to the walk's end: a machine has applied such a module only after the node-engine's report and prov.applied; a failed one is a failed apply.
Checks: MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh passes. Issue 630 (release 57) and issue 672 carry notes on this.
Reviewer's checklist: the wording matches ADR 0360's clauses 1, 2, 7, 8 and ADR 0362's clauses; no node names (hq is public); glossary words.
ADR 0360 (accepted 2026-10-14) sends a merge's builds to every machine at once, with no first-machine gate. Design 57 assumed that gate in two places:
- **What a release costs:** a fault on the release's first node held the release. Now the lab rehearsal is the only check before release 57 reaches every node; a failed apply or a failed `prov.applied` is named in the walk's end, raises apply-failing and is fixed forward.
- **P6 (issue 672):** the gate counted a provisioned module healthy only after `prov.applied` (`gateFacts`). ADR 0362 (proposed) moves that wait to the walk's end: a machine has applied such a module only after the node-engine's report and `prov.applied`; a failed one is a failed apply.
Checks: `MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh` passes. Issue 630 (release 57) and issue 672 carry notes on this.
Reviewer's checklist: the wording matches ADR 0360's clauses 1, 2, 7, 8 and ADR 0362's clauses; no node names (hq is public); glossary words.
ADR 0360 sends a merge's builds to every machine at once, so release 57
has no first node to hold it and P6 can no longer wait at a gate. ADR 0362
moves the wait for the provisioner to the walk's end.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deliverynovox/hq@bafc7b7d05dd — delivered since 2026-10-14T18:15:29Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-14 18:12 (new) → proposed (announced): novox/hq#353's head announced
2026-10-14 18:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-14 18:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-14 18:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-14 18:15 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-delivery:view -->
**Delivery** `novox/hq@bafc7b7d05dd` — **delivered** since 2026-10-14T18:15:29Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-14 18:12 (new) → proposed (announced): novox/hq#353's head announced
- 2026-10-14 18:14 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-14 18:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-14 18:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-14 18:15 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`.
Checked: the diff against ADR 0360 (accepted; clauses 1, 2, 7, 8) and ADR 0362 (proposed), ADR 0349 clause 15, the rest of design 57 for first-machine-gate assumptions, node names, glossary, front matter. MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh passes (exit 0). No node names. The only remaining "gate" words are the merge gate (the pull-request check), which is fine. P6 matches ADR 0362 clauses 1 and 2, and the release passage matches ADR 0360 clauses 1, 2 and 8.
Required:
Fix forward goes to main, not to the release's branches. "is fixed forward with a new merge into the release's branches": the walk runs after each repository's feat/57-config-and-provisioning branch has reached main (the paragraph above says so), so a merge into those branches delivers nothing. A fault seen after the walk is fixed with a new pull request into main (ADR 0360 §8: "fixes the cause with a new merge"). The old text had the same flaw, but this PR rewrote the sentence, so fix it here.
"the lab rehearsal is the only check before it reaches every node" overstates. The merge gate and repo check (mesh/merge-gate, mesh/repo-check) also run before the walk. Say "the only live check" (or "the only check that runs it").
Front matter: add ADR 0360. The changed passages rest on ADR 0360 (accepted), and the PR title names it, but decisions: only gains ADR 0362 (proposed). List both.
Not blocking:
4. ADR 0362 is still proposed. P6 states its rule as settled. Consider "(ADR 0362, proposed)" until it is accepted, because ADR 0349 §15 (the gate wait) is formally still in force until 0362 is accepted.
5. ADR 0360 §7 also names machines silent past ApplySilentAfter (fifteen minutes) in the walk's end. The release passage mentions only failed applies. That is acceptable, but one clause on silence would make it complete.
6. Glossary: release is defined as "a person's word that a held delivery goes on … Used in this sense only". Design 57 uses "release" for the bundled delivery throughout (this predates the PR, and the PR adds "the release has no first node" and "the release's branches"). This needs a follow-up: either a glossary word for it or a rewording to "delivery group" (ADR 0239 §2).
Verdict: CHANGES at c957fcc6d751ad25c5a5aa960cd69bf634970d05
Checked: the diff against ADR 0360 (accepted; clauses 1, 2, 7, 8) and ADR 0362 (proposed), ADR 0349 clause 15, the rest of design 57 for first-machine-gate assumptions, node names, glossary, front matter. `MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh` passes (exit 0). No node names. The only remaining "gate" words are the merge gate (the pull-request check), which is fine. P6 matches ADR 0362 clauses 1 and 2, and the release passage matches ADR 0360 clauses 1, 2 and 8.
Required:
1. **Fix forward goes to main, not to the release's branches.** "is fixed forward with a new merge into the release's branches": the walk runs after each repository's `feat/57-config-and-provisioning` branch has reached main (the paragraph above says so), so a merge into those branches delivers nothing. A fault seen after the walk is fixed with a new pull request into main (ADR 0360 §8: "fixes the cause with a new merge"). The old text had the same flaw, but this PR rewrote the sentence, so fix it here.
2. **"the lab rehearsal is the only check before it reaches every node" overstates.** The merge gate and repo check (`mesh/merge-gate`, `mesh/repo-check`) also run before the walk. Say "the only live check" (or "the only check that runs it").
3. **Front matter: add ADR 0360.** The changed passages rest on ADR 0360 (accepted), and the PR title names it, but `decisions:` only gains ADR 0362 (proposed). List both.
Not blocking:
4. ADR 0362 is still proposed. P6 states its rule as settled. Consider "(ADR 0362, proposed)" until it is accepted, because ADR 0349 §15 (the gate wait) is formally still in force until 0362 is accepted.
5. ADR 0360 §7 also names machines silent past ApplySilentAfter (fifteen minutes) in the walk's end. The release passage mentions only failed applies. That is acceptable, but one clause on silence would make it complete.
6. Glossary: **release** is defined as "a person's word that a held delivery goes on … Used in this sense only". Design 57 uses "release" for the bundled delivery throughout (this predates the PR, and the PR adds "the release has no first node" and "the release's branches"). This needs a follow-up: either a glossary word for it or a rewording to "delivery group" (ADR 0239 §2).
The pull requests' checks still run before the walk, and by then the
release's branches have reached main. Name the silent machine too, and
list ADR 0360, which the passages rest on (review comment 12348).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
I reviewed commit 5e49393 on top of c957fcc. MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh passes (exit 0), and the file still names no nodes.
Finding 1 is fixed: a fix forward now goes in a new pull request into main.
Finding 2 is fixed: "after the pull requests' checks, the lab rehearsal is the only live check" is accurate.
Finding 3 is fixed: the front matter lists ADR 0360 and ADR 0362.
Finding 5 is fixed: a machine silent past fifteen minutes (ApplySilentAfter, ADR 0360 §7) is named.
Not blocking: "either is fixed forward" also covers a silent machine. A machine can be silent because it is asleep or off, which is normal. Its send is then the backlog walk's job (ADR 0360 §10), so it needs no new pull request. Consider "a failed one is fixed forward …; a silent one gets its builds from the backlog walk when it is heard from" in a later edit.
Finding 6 (the word "release") is left to its own issue, as agreed.
Verdict: APPROVE at 5e493934a58361309b4c7349117a1fa81dfadea3
I reviewed commit 5e49393 on top of c957fcc. `MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh` passes (exit 0), and the file still names no nodes.
1. Finding 1 is fixed: a fix forward now goes in a new pull request into main.
2. Finding 2 is fixed: "after the pull requests' checks, the lab rehearsal is the only live check" is accurate.
3. Finding 3 is fixed: the front matter lists ADR 0360 and ADR 0362.
4. Finding 5 is fixed: a machine silent past fifteen minutes (ApplySilentAfter, ADR 0360 §7) is named.
5. Not blocking: "either is fixed forward" also covers a silent machine. A machine can be silent because it is asleep or off, which is normal. Its send is then the backlog walk's job (ADR 0360 §10), so it needs no new pull request. Consider "a failed one is fixed forward …; a silent one gets its builds from the backlog walk when it is heard from" in a later edit.
6. Finding 6 (the word "release") is left to its own issue, as agreed.
A machine that says nothing is often asleep; its builds wait for the
backlog walk (ADR 0360 clause 10), so no new pull request is needed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Commit bafc7b7 fixes the earlier note. A failed apply is fixed forward with a new pull request into main. A silent machine is named and gets its builds from the backlog walk once it is heard from, which matches ADR 0360 §7 and §10.
MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh passes (exit 0). The commit adds no node names and no glossary words outside their defined sense.
Verdict: APPROVE at bafc7b7d05ddd2a31f02ca096c5f10a105880c61
1. Commit bafc7b7 fixes the earlier note. A failed apply is fixed forward with a new pull request into main. A silent machine is named and gets its builds from the backlog walk once it is heard from, which matches ADR 0360 §7 and §10.
2. `MESH_CATALOG_DIR=../mesh-catalog sh merge-check.sh` passes (exit 0). The commit adds no node names and no glossary words outside their defined sense.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ADR 0360 (accepted 2026-10-14) sends a merge's builds to every machine at once, with no first-machine gate. Design 57 assumed that gate in two places:
prov.appliedis named in the walk's end, raises apply-failing and is fixed forward.prov.applied(gateFacts). ADR 0362 (proposed) moves that wait to the walk's end: a machine has applied such a module only after the node-engine's report andprov.applied; a failed one is a failed apply.Checks:
MESH_CATALOG_DIR=../mesh-catalog sh merge-check.shpasses. Issue 630 (release 57) and issue 672 carry notes on this.Reviewer's checklist: the wording matches ADR 0360's clauses 1, 2, 7, 8 and ADR 0362's clauses; no node names (hq is public); glossary words.
Delivery
novox/hq@bafc7b7d05dd— delivered since 2026-10-14T18:15:29ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: CHANGES at
c957fcc6d7Checked: the diff against ADR 0360 (accepted; clauses 1, 2, 7, 8) and ADR 0362 (proposed), ADR 0349 clause 15, the rest of design 57 for first-machine-gate assumptions, node names, glossary, front matter.
MESH_CATALOG_DIR=../mesh-catalog sh merge-check.shpasses (exit 0). No node names. The only remaining "gate" words are the merge gate (the pull-request check), which is fine. P6 matches ADR 0362 clauses 1 and 2, and the release passage matches ADR 0360 clauses 1, 2 and 8.Required:
feat/57-config-and-provisioningbranch has reached main (the paragraph above says so), so a merge into those branches delivers nothing. A fault seen after the walk is fixed with a new pull request into main (ADR 0360 §8: "fixes the cause with a new merge"). The old text had the same flaw, but this PR rewrote the sentence, so fix it here.mesh/merge-gate,mesh/repo-check) also run before the walk. Say "the only live check" (or "the only check that runs it").decisions:only gains ADR 0362 (proposed). List both.Not blocking:
4. ADR 0362 is still proposed. P6 states its rule as settled. Consider "(ADR 0362, proposed)" until it is accepted, because ADR 0349 §15 (the gate wait) is formally still in force until 0362 is accepted.
5. ADR 0360 §7 also names machines silent past ApplySilentAfter (fifteen minutes) in the walk's end. The release passage mentions only failed applies. That is acceptable, but one clause on silence would make it complete.
6. Glossary: release is defined as "a person's word that a held delivery goes on … Used in this sense only". Design 57 uses "release" for the bundled delivery throughout (this predates the PR, and the PR adds "the release has no first node" and "the release's branches"). This needs a follow-up: either a glossary word for it or a rewording to "delivery group" (ADR 0239 §2).
Verdict: APPROVE at
5e493934a5I reviewed commit
5e49393on top ofc957fcc.MESH_CATALOG_DIR=../mesh-catalog sh merge-check.shpasses (exit 0), and the file still names no nodes.Verdict: APPROVE at
bafc7b7d05bafc7b7fixes the earlier note. A failed apply is fixed forward with a new pull request into main. A silent machine is named and gets its builds from the backlog walk once it is heard from, which matches ADR 0360 §7 and §10.MESH_CATALOG_DIR=../mesh-catalog sh merge-check.shpasses (exit 0). The commit adds no node names and no glossary words outside their defined sense.