ADR 0594, first group: the node agent keeps the bus server unless the want is warranted #201

2026-11-03T08:21:22Z

mesh-tools commented

2026-11-03 08:21:22 +00:00

Under issue 774, ADR 0594 (accepted 2026-11-03). Group feat/774-bus-want with mesh-sdk (pinned at 959b1575); delivered before mesh-delivery's assigner change, which writes a bus want only to a node agent whose have says it keeps the server.

H1: Scope.Keep and the action kept-as-it-runs; the keep is decided once before anything moves, and only the runtime's own 'not there' counts as absent (an inspect error fails the apply, nothing written).
H2-H4: an unmarked bus want applies files, accounts and tools and keeps the server; the record judgement covers the server alone; a warranted want (put or operator) replaces the server, its warrant standing as the person's yes (lead's ruling, issue 774 note 92); the have names the applied fingerprint and Server (falling back to the old build name), and Server = fp when the server was made anew.
A removed bus want removes everything but the bus server and says once that it stays until a warranted want removes it.
H5: the node have says keeps bus-server. H6: a runner seam and TestNatsTheBusServerIsKeptUntilAWarrantedWantReplacesIt (real embedded bus): an unmarked want writes nats.conf and never removes, makes, stops, restarts or renames the server; a warranted want makes it once and Server == fp.

Tests: one new integration test (7 of 50); every other case a row; each fails without its change. Reviewer notes kept for later: the FP fallback in serverOf has no row; a kept archive deleted by hand is rewritten while the have names the old server.

Reviewed-by: review-774-engine@shanks at 2c5f818d15

Under issue 774, ADR 0594 (accepted 2026-11-03). Group feat/774-bus-want with mesh-sdk (pinned at 959b1575); delivered before mesh-delivery's assigner change, which writes a bus want only to a node agent whose have says it keeps the server. - H1: Scope.Keep and the action kept-as-it-runs; the keep is decided once before anything moves, and only the runtime's own 'not there' counts as absent (an inspect error fails the apply, nothing written). - H2-H4: an unmarked bus want applies files, accounts and tools and keeps the server; the record judgement covers the server alone; a warranted want (put or operator) replaces the server, its warrant standing as the person's yes (lead's ruling, issue 774 note 92); the have names the applied fingerprint and Server (falling back to the old build name), and Server = fp when the server was made anew. - A removed bus want removes everything but the bus server and says once that it stays until a warranted want removes it. - H5: the node have says keeps bus-server. H6: a runner seam and TestNatsTheBusServerIsKeptUntilAWarrantedWantReplacesIt (real embedded bus): an unmarked want writes nats.conf and never removes, makes, stops, restarts or renames the server; a warranted want makes it once and Server == fp. Tests: one new integration test (7 of 50); every other case a row; each fails without its change. Reviewer notes kept for later: the FP fallback in serverOf has no row; a kept archive deleted by hand is rewritten while the have names the old server. Reviewed-by: review-774-engine@shanks at 2c5f818d152201fef9b86ade5ea5feeee3859a12

mesh-tools added 6 commits 2026-11-03 08:21:22 +00:00

Pin mesh-sdk at the bus-want group's head 959b157, so the node agent reads the warrant, the server's fingerprint and the server's list (issue 774) 089ac78007

An apply leaves the resources its scope keeps as they run, so the bus server is not replaced by an unwarranted want (ADR 0594 §2) ffcd8f6d61

The node agent keeps the bus server unless the want carries the warrant's mark, and the bus's have says what the server runs (ADR 0594 §2-§4, §6) 9fd5429853

The node's own key says its agent keeps the bus server, so the assigner writes the bus want only to such a node (ADR 0594 §8) 052004d1cf

The node agent's applies run through a runner its options name, and one integration test proves an unwarranted bus want keeps the server and a warranted one replaces it (ADR 0594 §2-§4, §8) a096abac92

Review round 1 of the bus want: a removal keeps the bus server, the have says a server made anew runs the want's fingerprint, the old build is read before the first write, and an unanswered inspect fails the apply rather than replacing the server (ADR 0594 §2, §4)

mesh/delivery-group group feat/774-bus-want rejected: composed together: the checker's verdict at the members' heads (a0ab6ce2e316): novox

Details

mesh/delivery closed: the pull request closed unmerged

Details

mesh/check failed: novox: not composed on novox: nats has not been built for this mesh: server is its "server" artifact… | 2c5f818d1522 on 798d73eb11e9

2c5f818d15

mesh-tools commented

2026-11-03 08:21:25 +00:00

Delivery novox/mesh-host@2c5f818d1522 — closed since 2026-11-03T10:12:30Z

Transitions

2026-11-03 08:21 (new) → proposed (announced): novox/mesh-host#201's head announced
2026-11-03 08:21 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-11-03 10:12 ready → closed (closed): the pull request closed unmerged

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-host@2c5f818d1522` — **closed** since 2026-11-03T10:12:30Z **Transitions** - 2026-11-03 08:21 (new) → proposed (announced): novox/mesh-host#201's head announced - 2026-11-03 08:21 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-11-03 10:12 ready → closed (closed): the pull request closed unmerged 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 closed this pull request

2026-11-03 10:12:30 +00:00

mesh-tools commented

2026-11-03 10:12:30 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 959b1575a8c1 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools commented

2026-11-03 10:12:33 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 2c5f818d15 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 2c5f818d1522 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#201