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:`.
Deliverynovox/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`.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 onoperator-channelwith 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 newwarrantedverb 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: acceptedin the record, and add it to to-be 36'sdecisions:.Delivery
novox/hq@b18bf66ae235— delivered since 2026-10-10T10:10:03ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.3ea30b004atob18bf66ae2