Gives ADR 0346 (proposed in the knowledge base) its home in design 27, beside ADR 0202's paragraph: a served value may name the provider's own composed names (${bound:<requirement>:name} and its siblings), filled on both paths, and left out with the plan saying so where the providing machine composes no such name.
For issue 624: the forge serves the package registry's public root, so the lab can trust a tarball's address without a second copy of the forge's public name.
Checks run locally: records.py, index.py, cycle.py, words.py all pass.
Gives ADR 0346 (proposed in the knowledge base) its home in design 27, beside ADR 0202's paragraph: a served value may name the provider's own composed names (`${bound:<requirement>:name}` and its siblings), filled on both paths, and left out with the plan saying so where the providing machine composes no such name.
For issue 624: the forge serves the package registry's public root, so the lab can trust a tarball's address without a second copy of the forge's public name.
Checks run locally: records.py, index.py, cycle.py, words.py all pass.
Deliverynovox/hq@a54b1eaab9fc — delivered since 2026-10-13T18:34:13Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 14:40 (new) → proposed (announced): novox/hq#345's head announced
2026-10-13 14:44 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 14:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 15:27 ready → proposed (trunk moved): out of date: judged against trunk 471f99344b, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged
2026-10-13 18:30 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 18:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 18:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 18:34 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@a54b1eaab9fc` — **delivered** since 2026-10-13T18:34:13Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 14:40 (new) → proposed (announced): novox/hq#345's head announced
- 2026-10-13 14:44 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 14:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 15:27 ready → proposed (trunk moved): out of date: judged against trunk 471f99344b8d, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is merged
- 2026-10-13 18:30 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 18:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 18:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-13 18:34 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`.
Verdict: approve at a54b1eaa. It can merge now, independently of the code.
Independent review (issue 624, ADR 0346).
Design 27 gains ADR 0346 in decisions: and updated: 2026-10-13. The new paragraph matches the record's clauses: the own names a value may say (name, internal-name, name-, internal-name-), both paths, the key left out and said in plan, and the check when the definition is read. It matches what mesh-controller #306 builds.
It is public-safe: role words only (the forge, the provider's machine). The npm path names only the org, which hq already names.
records.py, index.py, cycle.py and words.py all pass at the head. The branch merges into the current main (0f5aab1) without conflict.
Nit, not blocking: the "How it is checked" sentence does not say that a served ${bound:...|default:...} is refused too (ADR 0346 §3, checkServedOwnNames in #306).
Statuses read at review time: mesh/repo-check is pending, "out of date: judged against trunk 471f99344b, the trunk is now 0f5aab10b4e0". mesh/delivery is pending ("checking"). Ask for a recheck and merge on green.
Verdict: approve at a54b1eaa. It can merge now, independently of the code.
Independent review (issue 624, ADR 0346).
- Design 27 gains ADR 0346 in decisions: and updated: 2026-10-13. The new paragraph matches the record's clauses: the own names a value may say (name, internal-name, name-<local>, internal-name-<local>), both paths, the key left out and said in plan, and the check when the definition is read. It matches what mesh-controller #306 builds.
- It is public-safe: role words only (the forge, the provider's machine). The npm path names only the org, which hq already names.
- records.py, index.py, cycle.py and words.py all pass at the head. The branch merges into the current main (0f5aab1) without conflict.
Nit, not blocking: the "How it is checked" sentence does not say that a served ${bound:...|default:...} is refused too (ADR 0346 §3, checkServedOwnNames in #306).
Statuses read at review time: mesh/repo-check is pending, "out of date: judged against trunk 471f99344b8d, the trunk is now 0f5aab10b4e0". mesh/delivery is pending ("checking"). Ask for a recheck and merge on green.
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.
Gives ADR 0346 (proposed in the knowledge base) its home in design 27, beside ADR 0202's paragraph: a served value may name the provider's own composed names (
${bound:<requirement>:name}and its siblings), filled on both paths, and left out with the plan saying so where the providing machine composes no such name.For issue 624: the forge serves the package registry's public root, so the lab can trust a tarball's address without a second copy of the forge's public name.
Checks run locally: records.py, index.py, cycle.py, words.py all pass.
Delivery
novox/hq@a54b1eaab9fc— delivered since 2026-10-13T18:34:13ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
471f99344b, the trunk is now 0f5aab10b4e0; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Verdict: approve at
a54b1eaa. It can merge now, independently of the code.Independent review (issue 624, ADR 0346).
0f5aab1) without conflict.Nit, not blocking: the "How it is checked" sentence does not say that a served ${bound:...|default:...} is refused too (ADR 0346 §3, checkServedOwnNames in #306).
Statuses read at review time: mesh/repo-check is pending, "out of date: judged against trunk
471f99344b, the trunk is now 0f5aab10b4e0". mesh/delivery is pending ("checking"). Ask for a recheck and merge on green.