What: design 47's list of what ends without a person gains one entry. A merge whose walk said its modules unchanged in the walk record's delivery.unchanged is delivered. The walk's modules keep meaning what it builds. A module neither built nor said unchanged is read by issue 474's stranded rule as before. The entry names the tests that check it. The field was decided on issue 611 under the operator's standing rule on small design limits.
Why: issue 611. A delivery whose modules matched what runs was stopped as stranded, and the operator was asked about a change already on every machine.
Checked: records.py, index.py, cycle.py and words.py all pass (sh merge-check.sh).
Fixes issue 611 (design half).
after: novox/mesh-catalog#265
What: design 47's list of what ends without a person gains one entry. A merge whose walk said its modules unchanged in the walk record's `delivery.unchanged` is delivered. The walk's `modules` keep meaning what it builds. A module neither built nor said unchanged is read by issue 474's stranded rule as before. The entry names the tests that check it. The field was decided on issue 611 under the operator's standing rule on small design limits.
Why: issue 611. A delivery whose modules matched what runs was stopped as stranded, and the operator was asked about a change already on every machine.
Checked: records.py, index.py, cycle.py and words.py all pass (`sh merge-check.sh`).
Fixes issue 611 (design half).
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Transitions
2026-10-13 06:21 (new) → proposed (announced): novox/hq#340's head announced
2026-10-13 06:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 06:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 06:23 ready → proposed (trunk moved): out of date: judged against trunk 0e6bc1bc80, the trunk is now 8e6ca012c556; judged again on a recheck or when it is merged
2026-10-13 06:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 06:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 08:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 08:25 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@18a5b2ac1a48` — **delivered** since 2026-10-13T08:25:54Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `fix/611-an-unchanged-build-is-delivered`, in order: novox/hq@18a5b2ac1a48 → novox/mesh-controller@05576db018a4 → novox/mesh-catalog@2f5e97030a5c
- novox/mesh-controller@05576db018a4 before novox/mesh-catalog@2f5e97030a5c: built by
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Transitions**
- 2026-10-13 06:21 (new) → proposed (announced): novox/hq#340's head announced
- 2026-10-13 06:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 06:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 06:23 ready → proposed (trunk moved): out of date: judged against trunk 0e6bc1bc803c, the trunk is now 8e6ca012c556; judged again on a recheck or when it is merged
- 2026-10-13 06:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 06:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 08:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-13 08:25 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`.
No blocking findings in the text. The required checks at this head are not green, so this must not merge until a recheck passes (see the statuses below).
The paragraph matches what mesh-controller #295 and mesh-catalog #265 build. The walk's record says delivery.unchanged per module with why. The modules map keeps meaning what the walk builds. A delivery whose planned modules the walk all said unchanged is delivered whichever commit the walk carried. One with a module neither built nor said unchanged falls through to the stop rule below it. Both named tests exist at the PR heads: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns in mesh-controller (listed in its testdata/store-tests) and TestAMergeWhoseModulesMatchWhatRunsIsDelivered in mesh-delivery. I ran both, and they pass at their heads and fail on main.
The public-repository rule holds. The added text names no node, address, domain, path, username or credential, only roles, records, a field name and test names. sh merge-check.sh exits 0 at the head ("records: all checks passed", "cycle: 436 documents checked, the chain holds", "words: … none in running prose"). It also exits 0 with MESH_CATALOG_DIR set and with the head merged into the current trunk 8e6ca01. Note that merge-check.sh is mode 100644 here and on main, so ./merge-check.sh is refused and it runs as sh merge-check.sh.
Non-blocking: "A delivery whose every module the walk built or said unchanged is delivered" is not exact for one case. A walk that carried a later merge's commit, built some of the planned modules and said the rest unchanged leaves the delivery covered by that carrier, not delivered (mesh-delivery's covered row, since the Done row requires builtNoneOfIts when the walk carried a later commit). Suggest "is delivered, or covered when a walk carrying a later merge built some of them".
Statuses at the head: mesh/merge-gate pending and mesh/repo-check pending, both "out of date: judged against trunk 0e6bc1bc80, the trunk is now 8e6ca012c556; judged again on a recheck or when it is merged". mesh/delivery is pending ("checking"), and mesh/delivery-group is pending ("group fix/611-an-unchanged-build-is-delivered checking: 0 of 3 member(s) ready"). Ask mesh-delivery.recheck and merge only on the new verdict.
Verdict: approve at 18a5b2ac1a48c324c5dce67dd0483213bac89d1a
No blocking findings in the text. The required checks at this head are not green, so this must not merge until a recheck passes (see the statuses below).
The paragraph matches what mesh-controller #295 and mesh-catalog #265 build. The walk's record says delivery.unchanged per module with why. The modules map keeps meaning what the walk builds. A delivery whose planned modules the walk all said unchanged is delivered whichever commit the walk carried. One with a module neither built nor said unchanged falls through to the stop rule below it. Both named tests exist at the PR heads: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns in mesh-controller (listed in its testdata/store-tests) and TestAMergeWhoseModulesMatchWhatRunsIsDelivered in mesh-delivery. I ran both, and they pass at their heads and fail on main.
The public-repository rule holds. The added text names no node, address, domain, path, username or credential, only roles, records, a field name and test names. sh merge-check.sh exits 0 at the head ("records: all checks passed", "cycle: 436 documents checked, the chain holds", "words: … none in running prose"). It also exits 0 with MESH_CATALOG_DIR set and with the head merged into the current trunk 8e6ca01. Note that merge-check.sh is mode 100644 here and on main, so ./merge-check.sh is refused and it runs as sh merge-check.sh.
Non-blocking: "A delivery whose every module the walk built or said unchanged is delivered" is not exact for one case. A walk that carried a later merge's commit, built some of the planned modules and said the rest unchanged leaves the delivery covered by that carrier, not delivered (mesh-delivery's covered row, since the Done row requires builtNoneOfIts when the walk carried a later commit). Suggest "is delivered, or covered when a walk carrying a later merge built some of them".
Statuses at the head: mesh/merge-gate pending and mesh/repo-check pending, both "out of date: judged against trunk 0e6bc1bc803c, the trunk is now 8e6ca012c556; judged again on a recheck or when it is merged". mesh/delivery is pending ("checking"), and mesh/delivery-group is pending ("group fix/611-an-unchanged-build-is-delivered checking: 0 of 3 member(s) ready"). Ask mesh-delivery.recheck and merge only on the new verdict.
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.
after: novox/mesh-catalog#265
What: design 47's list of what ends without a person gains one entry. A merge whose walk said its modules unchanged in the walk record's
delivery.unchangedis delivered. The walk'smoduleskeep meaning what it builds. A module neither built nor said unchanged is read by issue 474's stranded rule as before. The entry names the tests that check it. The field was decided on issue 611 under the operator's standing rule on small design limits.Why: issue 611. A delivery whose modules matched what runs was stopped as stranded, and the operator was asked about a change already on every machine.
Checked: records.py, index.py, cycle.py and words.py all pass (
sh merge-check.sh).Fixes issue 611 (design half).
Delivery
novox/hq@18a5b2ac1a48— delivered since 2026-10-13T08:25:54ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
fix/611-an-unchanged-build-is-delivered, in order: novox/hq@18a5b2ac1a → novox/mesh-controller@05576db018 → novox/mesh-catalog@2f5e97030aTransitions
0e6bc1bc80, the trunk is now 8e6ca012c556; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
18a5b2ac1aNo blocking findings in the text. The required checks at this head are not green, so this must not merge until a recheck passes (see the statuses below).
The paragraph matches what mesh-controller #295 and mesh-catalog #265 build. The walk's record says delivery.unchanged per module with why. The modules map keeps meaning what the walk builds. A delivery whose planned modules the walk all said unchanged is delivered whichever commit the walk carried. One with a module neither built nor said unchanged falls through to the stop rule below it. Both named tests exist at the PR heads: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns in mesh-controller (listed in its testdata/store-tests) and TestAMergeWhoseModulesMatchWhatRunsIsDelivered in mesh-delivery. I ran both, and they pass at their heads and fail on main.
The public-repository rule holds. The added text names no node, address, domain, path, username or credential, only roles, records, a field name and test names. sh merge-check.sh exits 0 at the head ("records: all checks passed", "cycle: 436 documents checked, the chain holds", "words: … none in running prose"). It also exits 0 with MESH_CATALOG_DIR set and with the head merged into the current trunk
8e6ca01. Note that merge-check.sh is mode 100644 here and on main, so ./merge-check.sh is refused and it runs as sh merge-check.sh.Non-blocking: "A delivery whose every module the walk built or said unchanged is delivered" is not exact for one case. A walk that carried a later merge's commit, built some of the planned modules and said the rest unchanged leaves the delivery covered by that carrier, not delivered (mesh-delivery's covered row, since the Done row requires builtNoneOfIts when the walk carried a later commit). Suggest "is delivered, or covered when a walk carrying a later merge built some of them".
Statuses at the head: mesh/merge-gate pending and mesh/repo-check pending, both "out of date: judged against trunk
0e6bc1bc80, the trunk is now 8e6ca012c556; judged again on a recheck or when it is merged". mesh/delivery is pending ("checking"), and mesh/delivery-group is pending ("group fix/611-an-unchanged-build-is-delivered checking: 0 of 3 member(s) ready"). Ask mesh-delivery.recheck and merge only on the new verdict.