The put's words: delivery.Put, a want's put and hold marks, a grant that says which node's accounts it names (ADR 0546) #82

2026-10-25T20:30:23Z

mesh-tools commented

2026-10-25 20:30:23 +00:00

ADR 0546 (putting a version of a module on a node is one tool call: the assigner's put, held until released; approved by the operator 2026-10-25). The operator's ask: "putting version x of module y on node z should be a simple tool call". No seat and no compose verb: the controller takes no change, so the assigner serves the put as its own tools (mesh-delivery feat/put-version, opened after this merges).

delivery.Put with its key <node>.<module> and its steps (asked, build, compose, person, snapshot, wanted, holding, done, released, refused) and its check.
A want's put and hold marks and their refusals.
ControllerGrant.NamesNode: whether a grant names a module's accounts on a node (the assigner's rule 6 per node, issue 1945).
ViewAnswerFits refuses an option of level approve or destroy: the delivery view never answers an approve-level ask (ADR 0546 clause 10).

Checked: go test -race passes in delivery, catalogue and asks; go vet -tags integration ./... is clean. No top-level test functions added (1668 unit, 41 integration, unchanged). No try (recovery mode: the operator merges by hand).

Release order: this merges first; then the assigner's and the teller's pins in mesh-delivery move to the merged main commit, and mesh-delivery's PR opens.

Reviewed-by: review-put@shanks at d4ae4b6790

ADR 0546 (putting a version of a module on a node is one tool call: the assigner's put, held until released; approved by the operator 2026-10-25). The operator's ask: "putting version x of module y on node z should be a simple tool call". No seat and no compose verb: the controller takes no change, so the assigner serves the put as its own tools (mesh-delivery feat/put-version, opened after this merges). - `delivery.Put` with its key `<node>.<module>` and its steps (asked, build, compose, person, snapshot, wanted, holding, done, released, refused) and its check. - A want's `put` and `hold` marks and their refusals. - `ControllerGrant.NamesNode`: whether a grant names a module's accounts on a node (the assigner's rule 6 per node, issue 1945). - `ViewAnswerFits` refuses an option of level approve or destroy: the delivery view never answers an approve-level ask (ADR 0546 clause 10). Checked: go test -race passes in delivery, catalogue and asks; go vet -tags integration ./... is clean. No top-level test functions added (1668 unit, 41 integration, unchanged). No try (recovery mode: the operator merges by hand). Release order: this merges first; then the assigner's and the teller's pins in mesh-delivery move to the merged main commit, and mesh-delivery's PR opens. Reviewed-by: review-put@shanks at d4ae4b6790b86b8fabe620e5483c0011ebaed1dd

mesh-tools added 4 commits 2026-10-25 20:30:23 +00:00

The assigner's seat with put, release and puts, the controller's compose verb, a put's key and value, and the view answers no option that authorises (ADR 0546) c4f37c279a

A grant says whether it names a module's accounts on a node, for the assigner and the compose verb (ADR 0546) 20a6dc4920

No seat and no compose verb for the put: the controller takes no change, so the assigner serves the put as its own tools from compositions the controller already writes (ADR 0546) 2f6741b7f8

Say the put's tools, not a seat's verbs, in the put's words (ADR 0546)

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

Details

mesh/check pass d4ae4b6790b8 on db26f7e8b6f5 | unit 1102 run, 680 kept, 2 skipped | integration 1103 run, 722 kept, 2 skipped | over bound: unit (slow…

d4ae4b6790

mesh-tools commented

2026-10-25 20:30:28 +00:00

Delivery novox/mesh-sdk@d4ae4b6790b8 — merged since 2026-10-25T20:35:29Z

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

Transitions

2026-10-25 20:30 (new) → proposed (announced): novox/mesh-sdk#82's head announced
2026-10-25 20:32 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
2026-10-25 20:35 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@d4ae4b6790b8` — **merged** since 2026-10-25T20:35:29Z **Source** — source.main moved to novox/mesh-sdk@db26f7e8b6f5. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-25 20:30 (new) → proposed (announced): novox/mesh-sdk#82's head announced - 2026-10-25 20:32 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 - 2026-10-25 20:35 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 merged commit db26f7e8b6 into main

2026-10-25 20:35:28 +00:00

mesh-tools deleted branch feat/put-version

2026-10-25 20:35:29 +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#82