ADR 0286: a tool or verb marked in its manifest runs only on the operator's approval of that one call (issue 417) #302

Merged
mesh-admin merged 3 commits from feat/0286-approval-bound-call into main 2026-10-10 20:04:24 +00:00
Contributor

Graduates research 039 (a tool that needs a person's approval) into ADR 0286. Tracks issue 417 (the build); issue 418 (the file and account reads that must have tools before execute is marked).

What it decides:

  • needs-approval in a module's manifest (or a seat's definition) marks a tool or verb; the controller issues the mark in the runner's membership and withholds a marked tool from a runner that does not honour it.
  • The tool runner serving the call (the controller for its own verbs) asks through the existing operator-channel asks under the module's name, shows every argument (whole, or in shape with markers and a fingerprint, as ADR 0277), Approve/Decline at the level approve, expiry 60 minutes; the first call does nothing and says so.
  • The same call made again runs once on the warrant, checked from the router's record with the SDK's Warrant.For and Option.Performs over the act digest (address, node, build, every argument), within 30 minutes of the choice, claimed in the node's own file; recorded through mesh-controller.warranted.
  • Marked first: node-login-shell.execute (once issue 418's reads exist) and mesh-delivery.release.

Also: to-be 46 §10 amended and handed off (status in-progress, code named), §13 phase 7; pointer notes in ADRs 0259, 0266, 0268, 0272; glossary entry approval mark; as-is 13 states that no call is refused today; research 039 graduated.

Checks: sh merge-check.sh passes (records, index, cycle, words).

Graduates research 039 (a tool that needs a person's approval) into ADR 0286. Tracks issue 417 (the build); issue 418 (the file and account reads that must have tools before `execute` is marked). What it decides: - `needs-approval` in a module's manifest (or a seat's definition) marks a tool or verb; the controller issues the mark in the runner's membership and withholds a marked tool from a runner that does not honour it. - The tool runner serving the call (the controller for its own verbs) asks through the existing `operator-channel` asks under the module's name, shows every argument (whole, or in shape with markers and a fingerprint, as ADR 0277), Approve/Decline at the level approve, expiry 60 minutes; the first call does nothing and says so. - The same call made again runs once on the warrant, checked from the router's record with the SDK's `Warrant.For` and `Option.Performs` over the act digest (address, node, build, every argument), within 30 minutes of the choice, claimed in the node's own file; recorded through `mesh-controller.warranted`. - Marked first: `node-login-shell.execute` (once issue 418's reads exist) and `mesh-delivery.release`. Also: to-be 46 §10 amended and handed off (status in-progress, code named), §13 phase 7; pointer notes in ADRs 0259, 0266, 0268, 0272; glossary entry *approval mark*; as-is 13 states that no call is refused today; research 039 graduated. Checks: `sh merge-check.sh` passes (records, index, cycle, words).
Author
Contributor

Delivery novox/hq@8060c20fda3d — delivered since 2026-10-10T20:04:34Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-10 20:00 (new) → proposed (announced): novox/hq#302's head announced
  • 2026-10-10 20:02 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 20:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 20:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 20:04 published → delivered (done): nothing for a walk to move

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@8060c20fda3d` — **delivered** since 2026-10-10T20:04:34Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 20:00 (new) → proposed (announced): novox/hq#302's head announced - 2026-10-10 20:02 proposed → checked (checked): the verdict names this commit - 2026-10-10 20:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 20:04 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 20:04 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben force-pushed feat/0286-approval-bound-call from abcb2ea3d2 to 972ca4689e 2026-10-10 19:57:07 +00:00 Compare
jschoubben added 3 commits 2026-10-10 20:00:32 +00:00
Graduates research 039. The tool runner (and the controller for its own verbs) asks the operator
through the existing operator-channel asks and runs the exact call once on the warrant, reusing the
act digest and warrant check of ADR 0259 and the shown-in-shape form of ADRs 0274 and 0277, so
risky agent calls stop resting on the agent's restraint. Amends to-be 46 and hands it off.
Separate the release paragraph from the execute bullet, and say the third call asks again
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
8060c20fda
jschoubben force-pushed feat/0286-approval-bound-call from 5e699c13f2 to 8060c20fda 2026-10-10 20:00:32 +00:00 Compare
mesh-admin merged commit 750a1d54d4 into main 2026-10-10 20:04:24 +00:00
mesh-admin deleted branch feat/0286-approval-bound-call 2026-10-10 20:04:25 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#302