ADR 0277: a trusted setting is proposed through a verb and set on the operator's warrant, and a module's own secret is asked for and typed at the desk
#278
Merged
mesh-adminmerged 2 commits from decisions/0277-a-trusted-setting-is-proposed-and-set-on-the-operators-warrant into main2026-10-10 12:50:20 +00:00
The operator's direction (2026-10-10): "you should modify the settings yourself, I don't want to run manual commands on novox".
ADR 0277 (accepted, extends ADR 0274): a trusted setting (and clearing it) may be proposed through the settings verb by anyone the bus admits; it is set by the serving controller only on the operator's Approve through the operator channel, bound to the digest of the exact values shown; Decline/expiry discard; the warrant is recorded as a hand-act; the push afterwards stays a separate act. A module's own secret is asked for by the secret-ask verb and typed by the operator at the desk prompt (never on Telegram, never in an argument), bounded (one open ask per secret, three an hour), the prompt naming module, secret, machine and who asked.
Rejected option recorded: letting verbs set trusted settings outright (an agent would decide what root mounts and owns). Also rejected for now: a seat event for the set, because the installer's first user list in the node-engine's repository names every controller event one by one.
Code: mesh-controller feat/0277-settings-propose-and-secret-ask; mesh-catalog feat/0277-the-desk-prompt-names-who-asked (rofi's prompt names who asked). merge-check.sh green locally.
The operator's direction (2026-10-10): "you should modify the settings yourself, I don't want to run manual commands on novox".
**ADR 0277** (accepted, extends ADR 0274): a trusted setting (and clearing it) may be proposed through the `settings` verb by anyone the bus admits; it is set by the serving controller only on the operator's Approve through the operator channel, bound to the digest of the exact values shown; Decline/expiry discard; the warrant is recorded as a hand-act; the push afterwards stays a separate act. A module's own secret is asked for by the `secret-ask` verb and typed by the operator at the desk prompt (never on Telegram, never in an argument), bounded (one open ask per secret, three an hour), the prompt naming module, secret, machine and who asked.
Rejected option recorded: letting verbs set trusted settings outright (an agent would decide what root mounts and owns). Also rejected for now: a seat event for the set, because the installer's first user list in the node-engine's repository names every controller event one by one.
Amended with dated notes: issue 339's rule, ADR 0259 §10 step 7, ADR 0266; to-be 44 §1, 52 §2/§5, 46 §10, 13; glossary (*controller's terminal*, new *proposal*).
Code: mesh-controller `feat/0277-settings-propose-and-secret-ask`; mesh-catalog `feat/0277-the-desk-prompt-names-who-asked` (rofi's prompt names who asked). `merge-check.sh` green locally.
The operator does not want to run manual commands on the control node. Issue 339 made every trusted
setting the terminal's alone, and a module's own secret the terminal's or the give verb's: each a line
an agent could only hand the operator to type. ADR 0274's pattern is extended: an agent proposes, the
operator approves on a channel that proves who answered, the controller sets the layer on the warrant
bound to the exact values shown. A secret is asked for by a verb and typed at the desk, bounded, the
prompt naming who asked. The designs 44, 52, 46 and 13, issue 339, ADR 0259 and 0266 and the glossary
are amended with dated notes.
Deliverynovox/hq@35394468857c — delivered since 2026-10-10T12:50:41Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 12:43 (new) → proposed (announced): novox/hq#278's head announced
2026-10-10 12:44 proposed → checked (checked): the verdict names this commit
2026-10-10 12:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 12:50 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 12:50 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@35394468857c` — **delivered** since 2026-10-10T12:50:41Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 12:43 (new) → proposed (announced): novox/hq#278's head announced
- 2026-10-10 12:44 proposed → checked (checked): the verdict names this commit
- 2026-10-10 12:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 12:50 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 12:50 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`.
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's direction (2026-10-10): "you should modify the settings yourself, I don't want to run manual commands on novox".
ADR 0277 (accepted, extends ADR 0274): a trusted setting (and clearing it) may be proposed through the
settingsverb by anyone the bus admits; it is set by the serving controller only on the operator's Approve through the operator channel, bound to the digest of the exact values shown; Decline/expiry discard; the warrant is recorded as a hand-act; the push afterwards stays a separate act. A module's own secret is asked for by thesecret-askverb and typed by the operator at the desk prompt (never on Telegram, never in an argument), bounded (one open ask per secret, three an hour), the prompt naming module, secret, machine and who asked.Rejected option recorded: letting verbs set trusted settings outright (an agent would decide what root mounts and owns). Also rejected for now: a seat event for the set, because the installer's first user list in the node-engine's repository names every controller event one by one.
Amended with dated notes: issue 339's rule, ADR 0259 §10 step 7, ADR 0266; to-be 44 §1, 52 §2/§5, 46 §10, 13; glossary (controller's terminal, new proposal).
Code: mesh-controller
feat/0277-settings-propose-and-secret-ask; mesh-catalogfeat/0277-the-desk-prompt-names-who-asked(rofi's prompt names who asked).merge-check.shgreen locally.Delivery
novox/hq@35394468857c— delivered since 2026-10-10T12:50:41ZDelivery 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.