L3: mesh-vault mints, retires and signs; nats makes its certificate; messenger asks each engine (issue 774, ADR 0561), rebased onto L2 #556

2026-10-28T20:56:48Z

mesh-tools commented

2026-10-28 20:56:48 +00:00

L3 (issue 774, ADR 0561), rebased onto L2.

Group member with mesh-sdk, mesh-delivery, mesh-host and hq on feat/774-vault-mints-l2. mesh-vault pins mesh-sdk 8eafc0c exactly.

Under L2: mesh-vault reads mesh-delivery-assigner.placement, beside L2's watched assignments; mesh-config is as L2 has it (placement with the assignments while both stand) and is listed as an assignments reader; the check that only listed modules read the controller's assignments moved into checks/noplacement, as L2 deleted checks/placement.

At add6f14: main merged in, and the reviewed gate fix (d42d3e2, issue 1276) on top: in mesh-delivery-gate an answer stands only for the ask it answers, and an approved merge never handed says which member holds it and why. The gate kept the Decline of an earlier ask on this member's unchanged head and never merged the approved group (issue 1276, notes 15-16); the new head makes this member a fresh delivery, and the fix of that kind ships with it (the operator chose this recovery).

Tests: L3 adds 9 unit and 1 integration over main (as approved); the gate fix replaces tests within a table (count unchanged).

Reviewed-by: rev-l2@shanks at c193d2b389
Reviewed-by: rev-held2@shanks at d42d3e20db4b53c2dd08a90d17298d9449112981 (the gate fix)
Reviewed-by: rev-l3b@shanks at add6f143ca

L3 (issue 774, ADR 0561), rebased onto L2. Group member with mesh-sdk, mesh-delivery, mesh-host and hq on feat/774-vault-mints-l2. mesh-vault pins mesh-sdk 8eafc0c exactly. Under L2: mesh-vault reads mesh-delivery-assigner.placement, beside L2's watched assignments; mesh-config is as L2 has it (placement with the assignments while both stand) and is listed as an assignments reader; the check that only listed modules read the controller's assignments moved into checks/noplacement, as L2 deleted checks/placement. At add6f14: main merged in, and the reviewed gate fix (d42d3e2, issue 1276) on top: in mesh-delivery-gate an answer stands only for the ask it answers, and an approved merge never handed says which member holds it and why. The gate kept the Decline of an earlier ask on this member's unchanged head and never merged the approved group (issue 1276, notes 15-16); the new head makes this member a fresh delivery, and the fix of that kind ships with it (the operator chose this recovery). Tests: L3 adds 9 unit and 1 integration over main (as approved); the gate fix replaces tests within a table (count unchanged). Reviewed-by: rev-l2@shanks at c193d2b3897099f6773dabf9bdc6afe249dd66b7 Reviewed-by: rev-held2@shanks at d42d3e20db4b53c2dd08a90d17298d9449112981 (the gate fix) Reviewed-by: rev-l3b@shanks at add6f143ca236d4e965cb114d3f1798492640d0c

mesh-tools added 17 commits 2026-10-28 20:56:48 +00:00

mesh-vault: mint each account the grants part wants and the vault holds no value or adopted hash for, in the controller's shape, hashed before account-issued and secret-changed (issue 774, ADR 0561 §1, §2, §4) 0b9f19b612

mesh-vault: mint only while the controller's lease is handed away, read afresh before each mint, and say in vault_status what is held back and why (issue 774, ADR 0561 §3, §9) 1628db6c80

mesh-vault: retire an account the grants part no longer wants only within ADR 0230's bounds, keeping its value, and re-enable it when wanted again; account_retire for a person past the bound (issue 774, ADR 0561 §2) 5c1729523b

mesh-vault: serve issue-account, the hand path that mints one wanted account now, and record a rotation at most once per loaded list's revision; a covered account still never rotates in place (issue 774, ADR 0561 §4, §9) 2d57c9663a

mesh-vault: tell where modules stand and which node holds the bus from the catalogue's placement first, so the vault does not depend on the controller's assignments for them (issue 774, ADR 0549 §3, §5) 64e6688ec8

mesh-vault: prove the vault whole on a real bus mints only from the lease write, and try a failed mint again at the pass; adopt the operator key before the watches open (issue 774, ADR 0561 §1-§4) 411c1b8de8

mesh-vault: account_retire refuses while the controller holds the lease or before the wants are read whole, as the passes do (issue 774, review round 1) e6b913cac7

mesh-config resolves for the modules the catalogue's placement puts on a node alone, and the placement check refuses any other module that reads the controller's assignments unless listed with why (issue 774, ADR 0549 §3, §6) 6bbb8329e4

The placement check's list of modules still reading the controller's assignments only shrinks against the trunk's copy (issue 774, ADR 0529 clause 2) bd5f170af0

mesh-vault signs: its signing key and authority made once with their operator copies, the verb sign for a node's own certificate from bus state, the event signed, the state signers and the tools that read and reassert them (issue 774, ADR 0550 §2) c00005c141

nats: the bus's certificate command moves here from mesh-controller with the same output, made once and checked, so the bus module makes its own certificate when a mesh is raised from nothing (issue 774, design 47 L3 s11) ef618e8199

messenger: ask each machine's own engine whether it is root-free, the node seat node-engine's root-free, not the controller's (issue 774, ADR 0563 §6) 2043200201

mesh-vault: secret-ask answers the callers its manifest names, each named as the runtime proved it, within the same bounds; the controller's relay as before (issue 774, ADR 0563 §8) d3eb5cae80

mesh-vault: pin mesh-sdk 4e6e5cc, the L3 group's head rebased on L2 (issue 774) 24fad2b92a

Follow L2 under L3: the vault and mesh-config read the seat mesh-placement's placement, and the check that only listed modules read the controller's assignments moves into noplacement, as L2 deleted the placement check (issue 774, ADR 0567, ADR 0549 §3, §6) 5be6576117

mesh-config reads the placement beside the controller's assignments while both stand, as L2 has it and the vault does, and is listed as a reader of them (issue 774, ADR 0549 §5; re-review) 10447d8c1e

Pin mesh-sdk 8eafc0c, the L3 group's head on mesh-sdk main with #120 and #121 (issue 774)

mesh/delivery-group group feat/774-vault-mints-l2 ready: every member ready, and composed together they pass

Details

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check pass c193d2b38970 on 158348ede789 | unit 1319 run, 5401 kept, 47 skipped | integration 1359 run, 5490 kept, 49 skipped | over bound: unit, …

c193d2b389

mesh-tools commented

2026-10-28 20:56:56 +00:00

Delivery novox/mesh-catalog@add6f143ca23 — merged since 2026-10-29T07:44:24Z

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

Group feat/774-vault-mints-l2: novox/hq@7fd89de7cb, novox/mesh-catalog@add6f143ca, novox/mesh-delivery@17c79f25f0, novox/mesh-host@4f9227a186

composed together: pass — the checker's verdict at the members' heads (21d54fbf45b0)

Transitions

2026-10-29 01:17 (new) → proposed (announced): novox/mesh-catalog#556's head announced
2026-10-29 01:17 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-29 07:44 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-catalog@add6f143ca23` — **merged** since 2026-10-29T07:44:24Z **Source** — source.main moved to novox/mesh-catalog@1555241393fe. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feat/774-vault-mints-l2`: novox/hq@7fd89de7cb81, novox/mesh-catalog@add6f143ca23, novox/mesh-delivery@17c79f25f047, novox/mesh-host@4f9227a1860f - composed together: pass — the checker's verdict at the members' heads (21d54fbf45b0) **Transitions** - 2026-10-29 01:17 (new) → proposed (announced): novox/mesh-catalog#556's head announced - 2026-10-29 01:17 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-29 07:44 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-28 22:21:34 +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-28 22:50:50 +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-28 23:20:07 +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-28 23:37:45 +00:00

mesh-delivery: not merged. The merge of this pull request into main at c193d2b389 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-delivery: **not merged.** The merge of this pull request into main at c193d2b3897099f6773dabf9bdc6afe249dd66b7 was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.

mesh-tools commented

2026-10-29 00:57:15 +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.

jschoubben added 2 commits 2026-10-29 01:17:39 +00:00

Merge remote-tracking branch 'origin/main' into l3-mc-main b46089b698

mesh-delivery-gate: an answer stands only for the ask it answers, and a merge never handed says why

mesh/delivery merged: source.main moved to novox/mesh-catalog@1555241393fe

Details

mesh/delivery-group group feat/774-vault-mints-l2 merged: every member is merged

Details

mesh/check pass add6f143ca23 on 158348ede789 | unit 1601 run, 5122 kept, 47 skipped | integration 1637 run, 5215 kept, 49 skipped | over bound: unit, …

add6f143ca

On 2026-10-29 the group feat/774-vault-mints-l2 was approved and never handed: hq#495 kept a Decline of an earlier ask beside the Approve of the next, readyAsks skipped it and handTurn returned nil for every member, with no log line. The Approve and a new ask now clear an earlier Decline, a run's answer names its ask (answered_ask), an approved merge that waits for nothing and is not handed logs why once and is a stalled line, and delivery_turns lists no unwritten turn while the check gates no merge.

mesh-tools commented

2026-10-29 01:17:45 +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 1555241393 into main

2026-10-29 07:44:23 +00:00

mesh-tools deleted branch feat/774-vault-mints-l2

2026-10-29 07:44:24 +00:00

mesh-tools referenced this pull request

2026-10-29 08:43:44 +00:00

Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774) #557

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#556