Builds ADR 0457 (accepted; a correction of fact to its clause 2 is in the knowledge base's review). A merge the controller missed while it was redelivered (mesh-catalog #378, keycloak's sign-in fix, merged 2026-10-19 22:46 UTC) was never planned, and a person's Release of its hold did nothing (issue 1336).
catch_up.go: at start (after 30 s, retried each minute up to 20 times while a trunk is left for later) and beside each heard merge (that trunk only), read the last 50 merge commits of each catalogue trunk through the forge's API (askForgeApi /commits, as parentOf and manifestAt do); each merge with no record (MergeOf) is a gap, heard through hearMerge in the trunk's order, said as caught up in the log and the plan's words.
The warrant (clause 2): asks of mesh-delivery before release 3e by their key (merge---, keycloak #378's merge-378-b9104454f9a5-1 under the asker mesh-delivery); asks of mesh-delivery-teller by the heads the Approve is bound to: option.Performs of the merge act for a pull request asked alone, the published details for a group (issues 1411, 1415). Accepted as movedOnApprove accepts: the operator's ask, Warrant.For, Approve, the operator proved by the channel.
batches.go: hearMerge and the catch-up share factsOfMerge / mergeFacts.plans() (touches, later merges, owed-late, moves, a new module); a gap that would be planned with no warrant raises one merge-not-heard condition per repository and commit, kept open and cleared when planned or out of the window, in plain words (ADR 0253).
A forge, router or store that does not answer is logged and left for the next catch-up, never read as nothing to catch up.
Tests: catch_up_test.go (window, paging, warrants on the three real teller ids rebuilt from group and heads, refusals of another head, repository or a Decline, keycloak's id), the plain-words test, and integration tests (gaps planned in order, a heard merge catching up its trunk, fifty-one merges, no warrant raising one condition, a new-module gap, a forge that does not answer).
Checks before this pull request: try build-1792503873812327801 at this head passed (1448 unit tests in 2.39 s, the integration level).
Live after its delivery (ADR 0457's check): a plan of novox/mesh-catalog carrying c0880c4d (mesh-catalog #378) builds keycloak, and novox/mesh-catalog@b9104454f9 reads delivered.
Opened along the way: 1411, 1412, 1415, 1416.
Builds ADR 0457 (accepted; a correction of fact to its clause 2 is in the knowledge base's review). A merge the controller missed while it was redelivered (mesh-catalog #378, keycloak's sign-in fix, merged 2026-10-19 22:46 UTC) was never planned, and a person's Release of its hold did nothing (issue 1336).
- catch_up.go: at start (after 30 s, retried each minute up to 20 times while a trunk is left for later) and beside each heard merge (that trunk only), read the last 50 merge commits of each catalogue trunk through the forge's API (askForgeApi /commits, as parentOf and manifestAt do); each merge with no record (MergeOf) is a gap, heard through hearMerge in the trunk's order, said as caught up in the log and the plan's words.
- The warrant (clause 2): asks of mesh-delivery before release 3e by their key (merge-<pr>-<head12>-, keycloak #378's merge-378-b9104454f9a5-1 under the asker mesh-delivery); asks of mesh-delivery-teller by the heads the Approve is bound to: option.Performs of the merge act for a pull request asked alone, the published details for a group (issues 1411, 1415). Accepted as movedOnApprove accepts: the operator's ask, Warrant.For, Approve, the operator proved by the channel.
- batches.go: hearMerge and the catch-up share factsOfMerge / mergeFacts.plans() (touches, later merges, owed-late, moves, a new module); a gap that would be planned with no warrant raises one merge-not-heard condition per repository and commit, kept open and cleared when planned or out of the window, in plain words (ADR 0253).
- A forge, router or store that does not answer is logged and left for the next catch-up, never read as nothing to catch up.
Tests: catch_up_test.go (window, paging, warrants on the three real teller ids rebuilt from group and heads, refusals of another head, repository or a Decline, keycloak's id), the plain-words test, and integration tests (gaps planned in order, a heard merge catching up its trunk, fifty-one merges, no warrant raising one condition, a new-module gap, a forge that does not answer).
Checks before this pull request: try build-1792503873812327801 at this head passed (1448 unit tests in 2.39 s, the integration level).
Live after its delivery (ADR 0457's check): a plan of novox/mesh-catalog carrying c0880c4d (mesh-catalog #378) builds keycloak, and novox/mesh-catalog@b9104454f9a5 reads delivered.
Opened along the way: 1411, 1412, 1415, 1416.
Reviewed-by: review-1336@shanks at 3c7048f24e55bd56601838cb0b044c5b30ae875c
Issues: 1336
mesh/merge-gate head 3c7048f24e55 merged into trunk 1816e8753b07 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@3c7048f24e55 — delivered since 2026-10-20T14:08:28Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-20 13:57 (new) → proposed (announced): novox/mesh-controller#407's head announced
2026-10-20 14:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-20 14:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-20 14:07 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 14:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-20 14:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@3c7048f24e55` — **delivered** since 2026-10-20T14:08:28Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-20 13:57 (new) → proposed (announced): novox/mesh-controller#407's head announced
- 2026-10-20 14:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-20 14:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-20 14:07 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 14:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-20 14:08 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
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.
Builds ADR 0457 (accepted; a correction of fact to its clause 2 is in the knowledge base's review). A merge the controller missed while it was redelivered (mesh-catalog #378, keycloak's sign-in fix, merged 2026-10-19 22:46 UTC) was never planned, and a person's Release of its hold did nothing (issue 1336).
Tests: catch_up_test.go (window, paging, warrants on the three real teller ids rebuilt from group and heads, refusals of another head, repository or a Decline, keycloak's id), the plain-words test, and integration tests (gaps planned in order, a heard merge catching up its trunk, fifty-one merges, no warrant raising one condition, a new-module gap, a forge that does not answer).
Checks before this pull request: try build-1792503873812327801 at this head passed (1448 unit tests in 2.39 s, the integration level).
Live after its delivery (ADR 0457's check): a plan of novox/mesh-catalog carrying c0880c4d (mesh-catalog #378) builds keycloak, and novox/mesh-catalog@b9104454f9 reads delivered.
Opened along the way: 1411, 1412, 1415, 1416.
Reviewed-by: review-1336@shanks at
3c7048f24eIssues: 1336
Delivery
novox/mesh-controller@3c7048f24e55— delivered since 2026-10-20T14:08:28ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
3c7048f2Judged: head
3c7048f24e55merged into trunk1816e8753b07; read beside it: mesh-cataloga67f01963f0d, mesh-controller-main1816e8753b07, mesh-hostce1b97ad973d, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792504675720261865(builds --log build-1792504675720261865).