ADR 0222: a module is told where a mesh seat's holder is reached; the controller writes no file a seat's holder owns (issue 190) #113

2026-10-05T20:24:23Z

mesh-admin commented

2026-10-05 20:24:23 +00:00

ADR 0222 (accepted, extends 0082): ${seat:<mesh seat>:reach} without a binding (only mesh-artifact-store; empty answer drops the list member); the runtime's module states insecure-registries; the controller writes no file a seat's holder owns; generated resources meet the collision check; a unit still held is not given back when another record of it goes. Options weighed include an operator setting and requiring artifact-store via ${bound:} (rejected: a credential per machine's runtime, and a cycle — the store runs in the runtime).
ADR 0082 / 0102: dated "mechanism changed" notes (the README's pointer-back rule; issue 190 step 2 asks for them). Decisions untouched.
Issue 190: located-in widened; dated note: step 1 done, steps 2/3/5 decided, step 4's single push replaced by an order; fixed-by left empty until merge.

Code PRs, merge order: mesh-controller #62 → mesh-catalog #72 → (mesh-host #26 deployed) → mesh-controller #63.

Checks: records.py, index.py (index rewritten for 0222), cycle.py pass. Number 0222 because 0220 is on main and 0221 is taken on another branch.

- **ADR 0222** (accepted, extends 0082): `${seat:<mesh seat>:reach}` without a binding (only `mesh-artifact-store`; empty answer drops the list member); the runtime's module states `insecure-registries`; the controller writes no file a seat's holder owns; generated resources meet the collision check; a unit still held is not given back when another record of it goes. Options weighed include an operator setting and requiring `artifact-store` via `${bound:}` (rejected: a credential per machine's runtime, and a cycle — the store runs in the runtime). - **ADR 0082 / 0102**: dated "mechanism changed" notes (the README's pointer-back rule; issue 190 step 2 asks for them). Decisions untouched. - **Issue 190**: `located-in` widened; dated note: step 1 done, steps 2/3/5 decided, step 4's single push replaced by an order; `fixed-by` left empty until merge. Code PRs, merge order: mesh-controller #62 → mesh-catalog #72 → (mesh-host #26 deployed) → mesh-controller #63. Checks: `records.py`, `index.py` (index rewritten for 0222), `cycle.py` pass. Number 0222 because 0220 is on main and 0221 is taken on another branch.

mesh-admin added 1 commit 2026-10-05 20:24:23 +00:00

ADR 0222: a module is told where a mesh seat's holder is reached; the controller writes no file a seat's holder owns 93bed2147f

Issue 190's remaining steps: the runtime's module states the registry trust through
${seat:mesh-artifact-store:reach}, the private network stops writing it, generated resources
meet the collision check, and the rollout is an order rather than one push. ADR 0082 and 0102
get notes saying where their mechanism now lives.

jschoubben added 1 commit 2026-10-05 20:42:56 +00:00

Merge main into issues/190-controller-writes-no-owned-file; index regenerated dae33af8b0

mesh-admin merged commit 6e59281806 into main

2026-10-05 20:42:57 +00:00

mesh-admin deleted branch issues/190-controller-writes-no-owned-file

2026-10-05 20:42:58 +00:00

mesh-admin commented

2026-10-06 23:07:30 +00:00

Delivery novox/hq@6e5928180684 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#113 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@6e5928180684` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#113 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#113