A silent machine is caught up by the backlog walk, not fixed forward
mesh/merge-gate head bafc7b7d05dd merged into trunk dcb5d5ce3883 — pass: the change touches no module of the mesh's graph
mesh/repo-check head bafc7b7d05dd merged into trunk dcb5d5ce3883 — pass: its merge-check.sh passed
mesh/delivery delivered

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>
This commit is contained in:
2026-10-14 18:12:52 +00:00
co-authored by Claude Opus 5.5
parent 5e493934a5
commit bafc7b7d05
@@ -52,8 +52,9 @@ database consumer connecting) is first seen in the lab rehearsal, and a fault fo
release, not one package. A merge's builds go to every machine at once (ADR 0360), so the release has no
first node to hold it: after the pull requests' checks, the lab rehearsal is the only live check before it
reaches every node. A machine that fails to apply it, or whose provisioner reports a module's files failed
(ADR 0362), is named in the walk's end and raises apply-failing, and one that says nothing within fifteen
minutes is named silent; either is fixed forward with a new pull request into main.
(ADR 0362), is named in the walk's end and raises apply-failing, and is fixed forward with a new pull
request into main; one that says nothing within fifteen minutes is named silent and gets its builds from
the backlog walk once it is heard from (ADR 0360 §10).
**Nothing breaks on the way.** ADR 0349 clause 17: each file is filled the old way or the new way, never
both, by the form of its manifest, and the old forms stay accepted until the last module has moved.