ADR 0274 accepted, with its two limits: to-be 36 rests on it

02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md

@@ -1,6 +1,6 @@
 ---
 topic: what runs on it
-status: proposed
+status: accepted
 date: 2026-10-10
 deciders: jochen
 reconstructed: false

03-DESIGN/01-to-be/36-the-operators-agent-on-a-machine.md

@@ -4,6 +4,7 @@ status: in-progress
 code: [mesh-catalog modules/claude-code]
 updated: 2026-10-10
 decisions:
+  - 02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md
   - 02-DECISIONS/0273-the-agents-home-is-the-modules-and-the-operators-personal-rules-and-lessons-are-registered-through-it.md
   - 02-DECISIONS/0266-on-the-control-node-agents-run-under-an-account-of-their-own-that-cannot-become-root-without-a-person.md
   - 02-DECISIONS/0243-the-agent-module-removes-a-home-item-it-did-not-place-only-on-the-persons-word-and-keeps-a-copy.md
@@ -499,9 +500,7 @@ home goes through the two routes above.
 
 ## 11. Shared instruction sections an agent proposes and the operator approves
 
-*Added 2026-10-10 by [ADR 0274](../../02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md) (proposed). This section is built against that
-record while it awaits the operator's acceptance; the frontmatter names it once it is accepted, as `records.py` holds
-a design to accepted records only.*
+*Added 2026-10-10 by [ADR 0274](../../02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md).*
 
 An instruction section for every node, or for some, has two ways in: the controller's terminal (issue 340), and **a
 proposal an agent makes and the operator approves** on a channel that proves who answered. A hand-over, a rule

04-ISSUES/340-an-agent-can-plant-a-hook-in-every-agent-session-on-the-mesh/00-report.md

@@ -76,7 +76,7 @@ own settings file. It does not see a tool call that changes the managed files of
    operator's own home is not written from the tools (see "How it is checked"). In the operator's words: "once we build a UI, we
    can also update the context through it". A surface of the operator's own, which can tell the operator from
    an agent, is the intended way back.
-   > **Amended 2026-10-10 by [ADR 0274](../../02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md) (proposed).**
+   > **Amended 2026-10-10 by [ADR 0274](../../02-DECISIONS/0274-an-agent-proposes-a-shared-instruction-section-and-every-node-takes-it-only-on-the-operators-warrant-which-it-proves-itself.md).**
    > Instruction sections at the mesh and node scopes gain a second way beside the terminal: an agent proposes one
    > with `claude_code_instructions_propose`, and every node takes it only on the operator's warrant (an ask at the
    > level approve, answered on a channel that proves who answered), which each node proves from the router's own