Why: ADR 0325 §8 (accepted) has the controller send a machine the take of a shared folder on the operator's warrant; to-be 45's rule 1 asks every kind of state the core keeps to name its one writer. The controller half (mesh-controller, branch feat/325-identities-and-kept-folders) adds the subject mesh.node.<node>.ask.access-act.
What: one row in to-be 45 §1, after the setuid-search row: the controller writes it on the operator's warrant, the machine records the act, the engine verifies the mesh's signature and takes it or refuses.
**Why**: ADR 0325 §8 (accepted) has the controller send a machine the take of a shared folder on the operator's warrant; to-be 45's rule 1 asks every kind of state the core keeps to name its one writer. The controller half (mesh-controller, branch feat/325-identities-and-kept-folders) adds the subject `mesh.node.<node>.ask.access-act`.
**What**: one row in to-be 45 §1, after the setuid-search row: the controller writes it on the operator's warrant, the machine records the act, the engine verifies the mesh's signature and takes it or refuses.
**Checked**: `merge-check.sh` (records, index, cycle, words) passes.
The controller sends a machine the take act on the operator's warrant, on mesh.node.<node>.ask.access-act;
the machine verifies the mesh's signature and records the act. Rule 1 asks every kind of state to name its
one writer.
Deliverynovox/hq@7456e24563a9 — delivered since 2026-10-12T18:41:55Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-12 18:39 (new) → proposed (announced): novox/hq#333's head announced
2026-10-12 18:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-12 18:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 18:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 18:41 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@7456e24563a9` — **delivered** since 2026-10-12T18:41:55Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-12 18:39 (new) → proposed (announced): novox/hq#333's head announced
- 2026-10-12 18:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-12 18:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 18:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 18:41 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.
Why: ADR 0325 §8 (accepted) has the controller send a machine the take of a shared folder on the operator's warrant; to-be 45's rule 1 asks every kind of state the core keeps to name its one writer. The controller half (mesh-controller, branch feat/325-identities-and-kept-folders) adds the subject
mesh.node.<node>.ask.access-act.What: one row in to-be 45 §1, after the setuid-search row: the controller writes it on the operator's warrant, the machine records the act, the engine verifies the mesh's signature and takes it or refuses.
Checked:
merge-check.sh(records, index, cycle, words) passes.Delivery
novox/hq@7456e24563a9— delivered since 2026-10-12T18:41:55ZDelivery 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.