This PR adds ADR 0292, which records the design limit that mesh-controller #216 builds for issue 405. The session decided it under the operator's standing rule that small design limits are decided and recorded, and the operator may supersede it.
The record extends ADR 0283 and ADR 0240 rule 5:
Which consumers are covered. A wait covers a provision when its part is that provision's name, or when the secret it waits for is the provision's shared credential (ADR 0158). This is also the convention for module authors.
Who is held. A consumer is held under a provider that only waits for the operator only when a wait covers what the consumer's failing check needs. An unhealthy provider still holds its consumers as ADR 0240 rule 5 says.
Who is said on its own. A consumer that no wait covers raises its own condition, and that condition says its provider waits.
The held consumer's gate. It passes as a wait for a person (ADR 0254), and the verdict carries the wait. The option where the gate waits was rejected for ADR 0283 option 4's reason: a walk would wait on the operator, possibly for days. The record names the blind spot this accepts.
Severity.needs-operator stays a warning (ADR 0283 decision 5).
"The mechanism changed — 2026-10-11, by ADR 0292" notes under ADR 0240 rule 5 and ADR 0283 decision 1;
a section in to-be 48 §6, and ADR 0292 in that document's decisions:.
The two progressive-insight notes from the first version are removed.
I numbered the record as the highest decision number on main and on every open hq PR branch, plus one (0291 → 0292), and pushed at once. sh merge-check.sh passes.
This PR adds ADR 0292, which records the design limit that mesh-controller #216 builds for issue 405. The session decided it under the operator's standing rule that small design limits are decided and recorded, and the operator may supersede it.
The record extends ADR 0283 and ADR 0240 rule 5:
1. **Which consumers are covered.** A wait covers a provision when its `part` is that provision's name, or when the secret it waits for is the provision's shared credential (ADR 0158). This is also the convention for module authors.
2. **Who is held.** A consumer is held under a provider that only waits for the operator only when a wait covers what the consumer's failing check needs. An unhealthy provider still holds its consumers as ADR 0240 rule 5 says.
3. **Who is said on its own.** A consumer that no wait covers raises its own condition, and that condition says its provider waits.
4. **The held consumer's gate.** It passes as a wait for a person (ADR 0254), and the verdict carries the wait. The option where the gate waits was rejected for ADR 0283 option 4's reason: a walk would wait on the operator, possibly for days. The record names the blind spot this accepts.
5. **Severity.** `needs-operator` stays a warning (ADR 0283 decision 5).
Each rule says which test in #216 checks it.
It also adds:
- "The mechanism changed — 2026-10-11, by ADR 0292" notes under ADR 0240 rule 5 and ADR 0283 decision 1;
- a section in to-be 48 §6, and ADR 0292 in that document's `decisions:`.
The two progressive-insight notes from the first version are removed.
I numbered the record as the highest decision number on `main` and on every open hq PR branch, plus one (0291 → 0292), and pushed at once. `sh merge-check.sh` passes.
Deliverynovox/hq@2ea803acce81 — delivered since 2026-10-11T01:23:33Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-11 01:11 (new) → proposed (announced): novox/hq#309's head announced
2026-10-11 01:12 proposed → checked (checked): the verdict names this commit
2026-10-11 01:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 01:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 01:23 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@2ea803acce81` — **delivered** since 2026-10-11T01:23:33Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-11 01:11 (new) → proposed (announced): novox/hq#309's head announced
- 2026-10-11 01:12 proposed → checked (checked): the verdict names this commit
- 2026-10-11 01:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 01:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 01:23 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-admin
changed title from Notes on ADR 0240 rule 5 and ADR 0283 decision 1: what a provider waiting for the operator holds (issue 405) to ADR 0292: a consumer of the part a provider waits on is held under the wait, and passes its gate as a wait for a person (issue 405)2026-10-11 01:09:24 +00:00
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: FAIL — its merge-check.sh failed: 02-DECISIONS/0292-a-consumer-of-the-part-a-provider-waits-on-is-held-under-the-wait-and-passes-its-gate-as-a-wait-for-a-person.md: an accepted decision nothing in the cycle cites -- give it a home in a design doc's decisions:, a research became:, an issue, or 00-META
Run by the build seat on shanks as build-1791680941048622697 (builds --log build-1791680941048622697).
--- its merge-check.sh (go toolchain)
records: 277 decision records checked
records: all checks passed
index: 6 topics, 277 records, no stored list
cycle: 1 document(s) break the development cycle:
02-DECISIONS/0292-a-consumer-of-the-part-a-provider-waits-on-is-held-under-the-wait-and-passes-its-gate-as-a-wait-for-a-person.md: an accepted decision nothing in the cycle cites -- give it a home in a design doc's decisions:, a research became:, an issue, or 00-META
**Merge check** at `a6b08de8`
- `mesh/merge-gate`: **PASS** — the change touches no module of the mesh's graph
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: 02-DECISIONS/0292-a-consumer-of-the-part-a-provider-waits-on-is-held-under-the-wait-and-passes-its-gate-as-a-wait-for-a-person.md: an accepted decision nothing in the cycle cites -- give it a home in a design doc's decisions:, a research became:, an issue, or 00-META
Run by the build seat on shanks as `build-1791680941048622697` (`builds --log build-1791680941048622697`).
```
--- its merge-check.sh (go toolchain)
records: 277 decision records checked
records: all checks passed
index: 6 topics, 277 records, no stored list
cycle: 1 document(s) break the development cycle:
02-DECISIONS/0292-a-consumer-of-the-part-a-provider-waits-on-is-held-under-the-wait-and-passes-its-gate-as-a-wait-for-a-person.md: an accepted decision nothing in the cycle cites -- give it a home in a design doc's decisions:, a research became:, an issue, or 00-META
```
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.
This PR adds ADR 0292, which records the design limit that mesh-controller #216 builds for issue 405. The session decided it under the operator's standing rule that small design limits are decided and recorded, and the operator may supersede it.
The record extends ADR 0283 and ADR 0240 rule 5:
partis that provision's name, or when the secret it waits for is the provision's shared credential (ADR 0158). This is also the convention for module authors.needs-operatorstays a warning (ADR 0283 decision 5).Each rule says which test in #216 checks it.
It also adds:
decisions:.The two progressive-insight notes from the first version are removed.
I numbered the record as the highest decision number on
mainand on every open hq PR branch, plus one (0291 → 0292), and pushed at once.sh merge-check.shpasses.Delivery
novox/hq@2ea803acce81— delivered since 2026-10-11T01:23:33ZDelivery 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.Notes on ADR 0240 rule 5 and ADR 0283 decision 1: what a provider waiting for the operator holds (issue 405)to ADR 0292: a consumer of the part a provider waits on is held under the wait, and passes its gate as a wait for a person (issue 405)Merge check at
a6b08de8mesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: FAIL — its merge-check.sh failed: 02-DECISIONS/0292-a-consumer-of-the-part-a-provider-waits-on-is-held-under-the-wait-and-passes-its-gate-as-a-wait-for-a-person.md: an accepted decision nothing in the cycle cites -- give it a home in a design doc's decisions:, a research became:, an issue, or 00-METARun by the build seat on shanks as
build-1791680941048622697(builds --log build-1791680941048622697).