ADR 0274: an agent proposes a shared instruction section, and every node takes it only on the operator's warrant #268

Merged
mesh-admin merged 4 commits from decisions/0274-shared-instructions-on-the-operators-approval into main 2026-10-10 10:09:39 +00:00
Contributor

The operator (2026-10-10): "our claude-code module should have mcp-tools to add mesh-shared instructions/context".

ADR 0274 (status: proposed, deciders: the operator, for the operator to accept): an agent proposes an instruction section (a rule, a hand-over, shared context) for every node or some through claude_code_instructions_propose; the module asks the operator on operator-channel with Approve and Decline both at the level approve; every node proves the router's warrant itself from the router's own record, against an ask composed again from the proposal and the exact text's digest, and keeps the approved text in its own file (never rendered from the bus). Removal needs the same approval. Decline or expiry discards. Context is one mechanism: an instruction section. The controller's new warranted verb records the warrant in the hand-act log from the router's record.

Also: issue 340 decision 2 amended (marked, dated); to-be 36 gains §11 and its check rows (its frontmatter names ADR 0274 once accepted, as records.py holds a design to accepted records); glossary gains instruction section.

Code: mesh-catalog (claude-code) and mesh-controller (warranted) pull requests, each linking back.

Checks: records, index, cycle and words pass locally; merge-check.sh passes.

To accept: set status: accepted in the record, and add it to to-be 36's decisions:.

The operator (2026-10-10): "our claude-code module should have mcp-tools to add mesh-shared instructions/context". ADR 0274 (status: proposed, deciders: the operator, for the operator to accept): an agent proposes an instruction section (a rule, a hand-over, shared context) for every node or some through `claude_code_instructions_propose`; the module asks the operator on `operator-channel` with Approve and Decline both at the level approve; every node proves the router's warrant itself from the router's own record, against an ask composed again from the proposal and the exact text's digest, and keeps the approved text in its own file (never rendered from the bus). Removal needs the same approval. Decline or expiry discards. Context is one mechanism: an instruction section. The controller's new `warranted` verb records the warrant in the hand-act log from the router's record. Also: issue 340 decision 2 amended (marked, dated); to-be 36 gains §11 and its check rows (its frontmatter names ADR 0274 once accepted, as records.py holds a design to accepted records); glossary gains *instruction section*. Code: mesh-catalog (claude-code) and mesh-controller (`warranted`) pull requests, each linking back. Checks: records, index, cycle and words pass locally; merge-check.sh passes. **To accept:** set `status: accepted` in the record, and add it to to-be 36's `decisions:`.
Author
Contributor

Delivery novox/hq@b18bf66ae235 — delivered since 2026-10-10T10:10:03Z

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

Transitions

  • 2026-10-10 10:07 (new) → proposed (announced): novox/hq#268's head announced
  • 2026-10-10 10:07 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 10:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 10:10 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 10:10 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@b18bf66ae235` — **delivered** since 2026-10-10T10:10:03Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 10:07 (new) → proposed (announced): novox/hq#268's head announced - 2026-10-10 10:07 proposed → checked (checked): the verdict names this commit - 2026-10-10 10:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 10:10 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 10:10 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 added 4 commits 2026-10-10 10:06:54 +00:00
The operator asked for mesh tools to add shared instructions and context. Issue 340 made that text the
terminal's until a surface of the operator's own exists; the operator channel is that surface. Proposed,
for the operator to accept.
ADR 0274 accepted, with its two limits: to-be 36 rests on it
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
b18bf66ae2
jschoubben force-pushed decisions/0274-shared-instructions-on-the-operators-approval from 3ea30b004a to b18bf66ae2 2026-10-10 10:06:54 +00:00 Compare
mesh-admin merged commit 835d7acc1a into main 2026-10-10 10:09:39 +00:00
mesh-admin deleted branch decisions/0274-shared-instructions-on-the-operators-approval 2026-10-10 10:09:39 +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#268