Kept active after review: 012 (its minimum-viable-node questions: one-node closure, tier vs graph level, package versions, bundle tailoring) and 027 (packages from outside the distribution, secrets in the account's environment, per-machine sizing, what a module leaves behind) are not decided by any record.
Each closed 00-overview.md has status: and became: naming the ADRs and designs that decided it (for 009 and 019, what overtook it), and a short What it became / What overtook it section, the convention of 003, 005 and 008. 001 and 006 no longer restate their status in prose.
007 does not cite ADR 0143 (superseded by 0144); the grant question is answered by ADR 0224.
Leftovers given a home: issue 409 (a condition needing judgement handed to an agent; to-be 45 now points at it), issue 414 (where the record lives; to-be 06 now points at it), issue 410 (${setting:} in login-shell code), issues 415 and 416 (037's shared preference, and retention and log rotation).
023 left as it is: playbook 01's template has no became: field for an open effort.
sh merge-check.sh passes locally.
Issue 408: research efforts still said `active` after later ADRs and designs had answered or overtaken their questions.
- Graduated: 001, 006, 007, 010, 013, 017, 026, 037. Abandoned: 009, 019.
- Kept active after review: 012 (its minimum-viable-node questions: one-node closure, tier vs graph level, package versions, bundle tailoring) and 027 (packages from outside the distribution, secrets in the account's environment, per-machine sizing, what a module leaves behind) are not decided by any record.
- Each closed `00-overview.md` has `status:` and `became:` naming the ADRs and designs that decided it (for 009 and 019, what overtook it), and a short *What it became* / *What overtook it* section, the convention of 003, 005 and 008. 001 and 006 no longer restate their status in prose.
- 007 does not cite ADR 0143 (superseded by 0144); the grant question is answered by ADR 0224.
- Leftovers given a home: issue 409 (a condition needing judgement handed to an agent; to-be 45 now points at it), issue 414 (where the record lives; to-be 06 now points at it), issue 410 (`${setting:}` in login-shell code), issues 415 and 416 (037's shared preference, and retention and log rotation).
- 023 left as it is: playbook 01's template has no `became:` field for an open effort.
`sh merge-check.sh` passes locally.
Ten graduated and two abandoned efforts still said active, so the record
read as open questions that later ADRs and designs had answered. Each now
names in became: what decided or overtook it. To-be 45's undecided item
moves from research 017 to issue 409, and research 037's shell follow-up
is issue 410.
Deliverynovox/hq@907051c21d5d — delivered since 2026-10-10T19:51:55Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 19:48 (new) → proposed (announced): novox/hq#298's head announced
2026-10-10 19:49 proposed → checked (checked): the verdict names this commit
2026-10-10 19:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 19:51 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 19:51 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@907051c21d5d` — **delivered** since 2026-10-10T19:51:55Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 19:48 (new) → proposed (announced): novox/hq#298's head announced
- 2026-10-10 19:49 proposed → checked (checked): the verdict names this commit
- 2026-10-10 19:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 19:51 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 19:51 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`.
The review found questions no record decides: 012's minimum-viable-node
half and 027's packaging, secrets, sizing and leftovers questions, so both
stay active. Where the record lives (006) is issue 414, and 037's two
other leftovers are issues 415 and 416; to-be 06 now points at issue 414.
mesh-admin
changed title from Close twelve research efforts their decisions already settled (issue 408) to Close ten research efforts their decisions already settled (issue 408)2026-10-10 19:48:46 +00:00
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.
Issue 408: research efforts still said
activeafter later ADRs and designs had answered or overtaken their questions.00-overview.mdhasstatus:andbecame:naming the ADRs and designs that decided it (for 009 and 019, what overtook it), and a short What it became / What overtook it section, the convention of 003, 005 and 008. 001 and 006 no longer restate their status in prose.${setting:}in login-shell code), issues 415 and 416 (037's shared preference, and retention and log rotation).became:field for an open effort.sh merge-check.shpasses locally.Delivery
novox/hq@907051c21d5d— delivered since 2026-10-10T19:51: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.Close twelve research efforts their decisions already settled (issue 408)to Close ten research efforts their decisions already settled (issue 408)