A dated progressive insight in ADR 0266 §1: the operator chose on 2026-10-10 that the control node's agent account is nox, not agent. The name is the account argument of mesh-controller node agent-account, a node fact stated at the controller's terminal, so no code changes and the decision stands. No other record, design or issue names the account agent.
Why an insight and not a new record: the README's test is whether a reader who acted on the old text would be wrong about what was decided. What was decided is that the control node names an agent account of its own that cannot become root without a person; the name is a detail it does not rest on, and no later record cites it.
A second, forced change: any insight dated from 2026-10-09 holds the whole record to the deferral rule (issue 354, cycle.py), and the consequences' "each is left for a later record" (the ways §3 lists as not judged) had no tracking issue. A second insight there names issue 344, which gains gap 14 for them.
Checks: records, index, cycle, words pass locally.
A dated progressive insight in ADR 0266 §1: the operator chose on 2026-10-10 that the control node's agent account is `nox`, not `agent`. The name is the account argument of `mesh-controller node agent-account`, a node fact stated at the controller's terminal, so no code changes and the decision stands. No other record, design or issue names the account `agent`.
Why an insight and not a new record: the README's test is whether a reader who acted on the old text would be wrong about what was decided. What was decided is that the control node names an agent account of its own that cannot become root without a person; the name is a detail it does not rest on, and no later record cites it.
A second, forced change: any insight dated from 2026-10-09 holds the whole record to the deferral rule (issue 354, `cycle.py`), and the consequences' "each is left for a later record" (the ways §3 lists as not judged) had no tracking issue. A second insight there names issue 344, which gains gap 14 for them.
Checks: records, index, cycle, words pass locally.
Deliverynovox/hq@997e422a3226 — delivered since 2026-10-09T23:33:14Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 23:29 (new) → proposed (announced): novox/hq#264's head announced
2026-10-09 23:31 proposed → checked (checked): the verdict names this commit
2026-10-09 23:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 23:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 23:33 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@997e422a3226` — **delivered** since 2026-10-09T23:33:14Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 23:29 (new) → proposed (announced): novox/hq#264's head announced
- 2026-10-09 23:31 proposed → checked (checked): the verdict names this commit
- 2026-10-09 23:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 23:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 23:33 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.
A dated progressive insight in ADR 0266 §1: the operator chose on 2026-10-10 that the control node's agent account is
nox, notagent. The name is the account argument ofmesh-controller node agent-account, a node fact stated at the controller's terminal, so no code changes and the decision stands. No other record, design or issue names the accountagent.Why an insight and not a new record: the README's test is whether a reader who acted on the old text would be wrong about what was decided. What was decided is that the control node names an agent account of its own that cannot become root without a person; the name is a detail it does not rest on, and no later record cites it.
A second, forced change: any insight dated from 2026-10-09 holds the whole record to the deferral rule (issue 354,
cycle.py), and the consequences' "each is left for a later record" (the ways §3 lists as not judged) had no tracking issue. A second insight there names issue 344, which gains gap 14 for them.Checks: records, index, cycle, words pass locally.
Delivery
novox/hq@997e422a3226— delivered since 2026-10-09T23:33:14ZDelivery 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.