Delivery records are true at the source: the layouts for what a repository's merges reached (issue 1280) #102

2026-10-26T21:30:03Z

mesh-tools commented

2026-10-26 21:30:03 +00:00

Issue 1280, ADR 0556: a delivery's record is derived by the view from the wants and haves, not kept by the gate. This member carries the shared layouts the view, the indexer, the teller and the gate read: the indexer's taken state (the newest merge of each repository it took in) and what a merge reached. Member of the delivery group fix/delivery-records-true (mesh-sdk, mesh-delivery, mesh-catalog), one check for all three.

Merged with main up to 823d520 (L2); no conflicts.

Reviewed-by: review-delivered-b@shanks at 68d65e6bbf

Issue 1280, ADR 0556: a delivery's record is derived by the view from the wants and haves, not kept by the gate. This member carries the shared layouts the view, the indexer, the teller and the gate read: the indexer's `taken` state (the newest merge of each repository it took in) and what a merge reached. Member of the delivery group fix/delivery-records-true (mesh-sdk, mesh-delivery, mesh-catalog), one check for all three. Merged with main up to 823d520 (L2); no conflicts. Reviewed-by: review-delivered-b@shanks at 68d65e6bbf6134e080bba0c144a2b446effacabc

mesh-tools added 8 commits 2026-10-26 21:30:03 +00:00

Layouts of the indexer's taken and the view's reach, and the delivery seat's settle verb, so whether a merge is on the machines can be derived (issue 1280, ADR 0556) 43de3c937d

The view's reach carries the reached head and each change's source revision; nothing records a merge as delivered (ADR 0556 v8) 54a8afac73

A module's floor counts every running have, healthy or not; health stays in its words (ADR 0556 clause 2, insight) aa8e9afc7c

A settle ask's group and the act its options bind, shared by the gate and the teller (ADR 0556 clause 5) 5ecda46124

A settle ask's group begins with a colon, which no branch name holds, so a branch named settle/... still merges on its Approve (review of issue 1280) 1f70c4c0aa

A module with no floor holds no head back; a merge among its changes reads not yet on the machines (review of issue 1280, ADR 0556 clause 2) e44cbaf57f

Merge remote-tracking branch 'origin/main' into fix/delivery-records-true b4310dfb8e

Merge remote-tracking branch 'origin/main' into fix/delivery-records-true

mesh/delivery merged: source.main moved to novox/mesh-sdk@684acb922d99

Details

mesh/delivery-group group fix/delivery-records-true merged: every member is merged

Details

mesh/check checking 68d65e6bbf61 on 823d52051f03 | novox/mesh-sdk#102 in group fix/delivery-records-true

68d65e6bbf

mesh-tools commented

2026-10-26 21:30:06 +00:00

Delivery novox/mesh-sdk@68d65e6bbf61 — merged since 2026-10-26T21:48:45Z

Source — source.main moved to novox/mesh-sdk@684acb922d. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group fix/delivery-records-true: novox/mesh-catalog@c1cd8461bc, novox/mesh-delivery@c12b870104, novox/mesh-sdk@68d65e6bbf

Transitions

2026-10-26 21:30 (new) → proposed (announced): novox/mesh-sdk#102's head announced
2026-10-26 21:30 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-26 21:48 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-sdk@68d65e6bbf61` — **merged** since 2026-10-26T21:48:45Z **Source** — source.main moved to novox/mesh-sdk@684acb922d99. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/delivery-records-true`: novox/mesh-catalog@c1cd8461bc6e, novox/mesh-delivery@c12b870104e8, novox/mesh-sdk@68d65e6bbf61 **Transitions** - 2026-10-26 21:30 (new) → proposed (announced): novox/mesh-sdk#102's head announced - 2026-10-26 21:30 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-26 21:48 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools commented

2026-10-26 21:30:18 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools commented

2026-10-26 21:30:20 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit 684acb922d into main

2026-10-26 21:48:43 +00:00

mesh-tools deleted branch fix/delivery-records-true

2026-10-26 21:48:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-sdk#102