The parts serve the gate: the bridge performs owed acts and merges, the teller carries asks, the indexer reads source.main, the view shows asks (design 47 R3e, issues 1341-1345) #9

2026-10-20T06:36:08Z

mesh-tools commented

2026-10-20 06:36:08 +00:00

Design 47 release R3e (ADR 0437 §4-§10, ADR 0441 §5, ADR 0450). Delivery group feat/r3e-the-gate with mesh-catalog (the gate) and mesh-tools.

1341: the forge bridge performs the gate's owed acts (status, view, note, comment), keeping the revision acted at in its own bucket performed; a refusal is written on FORGE once.
1342: the bridge merges the member handed in merges.<g> with every approved head; stops at the first refusal.
1343: the teller carries the gate's asks to the router under each asking's own id (issue 1370), cancels an earlier asking on a rewrite, writes one answer per asking (an earlier asking's answer is replaced), raises and clears the condition keyed by the gate key; heads spelled lowercase as the gate does.
1344: the indexer stamps modules from source.main.
1345: the view lists open asks (an ask answered only when the answer's warrant names its id) and shows a have of phase removed as removed.

Review: three rounds by review-r3e@shanks. The last commit c93954e5 only re-pins mesh-sdk from ba684e54 to 88581d0a (main's merge of #47, the same go/ tree): the reviewed tree re-pinned.
Try build-1792478030333380826 passed (bridge, indexer, teller, view integration fresh).

Reviewed-by: review-r3e@shanks at bf59b5a27b (re-pinned as c93954e53c)

Design 47 release R3e (ADR 0437 §4-§10, ADR 0441 §5, ADR 0450). Delivery group feat/r3e-the-gate with mesh-catalog (the gate) and mesh-tools. - 1341: the forge bridge performs the gate's owed acts (status, view, note, comment), keeping the revision acted at in its own bucket `performed`; a refusal is written on FORGE once. - 1342: the bridge merges the member handed in `merges.<g>` with every approved head; stops at the first refusal. - 1343: the teller carries the gate's asks to the router under each asking's own id (issue 1370), cancels an earlier asking on a rewrite, writes one answer per asking (an earlier asking's answer is replaced), raises and clears the condition keyed by the gate key; heads spelled lowercase as the gate does. - 1344: the indexer stamps modules from `source.main`. - 1345: the view lists open asks (an ask answered only when the answer's warrant names its id) and shows a have of phase removed as removed. Review: three rounds by review-r3e@shanks. The last commit c93954e5 only re-pins mesh-sdk from ba684e54 to 88581d0a (main's merge of #47, the same go/ tree): the reviewed tree re-pinned. Try build-1792478030333380826 passed (bridge, indexer, teller, view integration fresh). Reviewed-by: review-r3e@shanks at bf59b5a27b79bd67d3a78ba3217d35f1cc13a89a (re-pinned as c93954e53c8ecc8167aad7c3c96fd3681aa663bd)

mesh-tools added 13 commits 2026-10-20 06:36:09 +00:00

Declare the bridge's performed bucket (issue 1341) 507fac41fe

Turn an owed key into the forge call that performs it, and a refusal into a refused message (issue 1341) 7686cfc55d

Test the bridge's two state buckets, heads and performed (issue 1341) a0883a174b

Perform the gate's owed acts once per revision from the bridge, a refusal written on FORGE (issue 1341) eeb5561a23

Merge the pull request a gate's merges key hands the bridge, with the Approve's heads, one pass stopping at a refusal (issue 1342) be5c1b371e

Grant the bridge's test principal only a read of the gate's buckets, as the controller composes it (issues 1341, 1342) 8ee56dbb5c

Carry the gate's merge asks to the router and write the operator's answer back, a warrant that does not hold said as a condition (issue 1343) 5ba1da5b82

Stamp the modules with the gate's source revision, read from source.main (issue 1344) 409c41d4ae

Add the indexer's source revision logic and its tests that the last commit named (issue 1344) 05c180cf87

Show the open asks in the delivery view: the gate's asks with no answer, in the table, the page and the command's JSON (issue 1345) 34f585106f

Ask under each asking's own router id, spell the heads in lower case as the gate does, show a removed have plainly; pin mesh-sdk ba684e5 (review round 1: G2, T1, issue 1370) 14e9d56a22

An answer to an earlier asking no longer blocks the next asking: the teller and the view tell the asking by the answer's warrant id (review round 2, R2-1) bf59b5a27b

Pin mesh-sdk to main's merge of #47 (88581d0a), the same tree as ba684e54 the review read

mesh/repo-check head c93954e53c8e merged into trunk 9c15112d935a beside mesh-catalog#380@cf5c0273 +1 more — pass: its merge-check.sh passed

Details

mesh/merge-gate head c93954e53c8e merged into trunk 9c15112d935a — pass: group feat/r3e-the-gate composed: every machine composes with the change as it did…

Details

mesh/delivery failed: its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

Details

mesh/delivery-group group feat/r3e-the-gate failed: a member failed

Details

c93954e53c

mesh-tools commented

2026-10-20 06:36:22 +00:00

Delivery novox/mesh-delivery@c93954e53c8e — failed since 2026-10-20T06:55:42Z

Delivery plan — builds mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view → novox, shanks; no bus step

tier 0: mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view
novox: receives mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller
shanks: receives mesh-delivery-view
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-view is judged on its first machine

Group feat/r3e-the-gate: novox/mesh-catalog@1d9c72c476, novox/mesh-delivery@c93954e53c, novox/mesh-tools@06e6721ed6

composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Transitions

2026-10-20 06:36 (new) → proposed (announced): novox/mesh-delivery#9's head announced
2026-10-20 06:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-20 06:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-20 06:51 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 06:51 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 06:55 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-delivery@c93954e53c8e` — **failed** since 2026-10-20T06:55:42Z **Delivery plan** — builds mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view → novox, shanks; no bus step - tier 0: mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller, mesh-delivery-view - novox: receives mesh-delivery-forge-bridge, mesh-delivery-indexer, mesh-delivery-teller - shanks: receives mesh-delivery-view - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-delivery-view is judged on its first machine **Group** `feat/r3e-the-gate`: novox/mesh-catalog@1d9c72c476f8, novox/mesh-delivery@c93954e53c8e, novox/mesh-tools@06e6721ed677 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Transitions** - 2026-10-20 06:36 (new) → proposed (announced): novox/mesh-delivery#9's head announced - 2026-10-20 06:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-20 06:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-20 06:51 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 06:51 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 06:55 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 2520cc4a88 into main

2026-10-20 06:49:19 +00:00

mesh-tools deleted branch feat/r3e-the-gate

2026-10-20 06:49:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#9