Follows hq#342 (merged), from the independent review of mesh-catalog#276: design 36 §12 now says a project is one entry of the projects directory and a path is relative with no empty, . or .. part, and a value in the state naming anything else is never taken. ADR 0343 says the same in clause 1 through a progressive insight (version 15, under the knowledge base's review).
sh merge-check.sh passes locally.
Follows hq#342 (merged), from the independent review of mesh-catalog#276: design 36 §12 now says a project is one entry of the projects directory and a path is relative with no empty, `.` or `..` part, and a value in the state naming anything else is never taken. ADR 0343 says the same in clause 1 through a progressive insight (version 15, under the knowledge base's review).
`sh merge-check.sh` passes locally.
Deliverynovox/hq@d70c189ed2ab — delivered since 2026-10-13T14:27:18Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 14:20 (new) → proposed (announced): novox/hq#343's head announced
2026-10-13 14:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 14:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 14:27 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 14:27 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@d70c189ed2ab` — **delivered** since 2026-10-13T14:27:18Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 14:20 (new) → proposed (announced): novox/hq#343's head announced
- 2026-10-13 14:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 14:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 14:27 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 14:27 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 added sentence in design 36 §12 says that a project is one entry of the projects directory and that a path is relative with no part empty, . or .., and that a value naming anything else is never taken. That matches NameProblem in mesh-catalog #276 at 305601d2 exactly. It is a safeguard on ADR 0343's clauses, not a new decision, so it belongs in the design. Role names only; mesh/repo-check passes.
Not blocking: the edited line is longer than its neighbours, so rewrap it. #276 also adds a warning when a memory file cannot be written on a node. One sentence under §12's conflict row would record it, ideally in the same PR as the fix that makes it clear (see my review on #276).
Order: merge this before or together with mesh-catalog #276. The branch names differ (design/367-memory-names and fix/367-memory-follows-the-operator), so they do not form a delivery group.
Verdict: approve at d70c189ed2ab033c458671c5330c7c7d87cc8d00
The added sentence in design 36 §12 says that a project is one entry of the projects directory and that a path is relative with no part empty, `.` or `..`, and that a value naming anything else is never taken. That matches `NameProblem` in mesh-catalog #276 at 305601d2 exactly. It is a safeguard on ADR 0343's clauses, not a new decision, so it belongs in the design. Role names only; mesh/repo-check passes.
Not blocking: the edited line is longer than its neighbours, so rewrap it. #276 also adds a warning when a memory file cannot be written on a node. One sentence under §12's conflict row would record it, ideally in the same PR as the fix that makes it clear (see my review on #276).
Order: merge this before or together with mesh-catalog #276. The branch names differ (design/367-memory-names and fix/367-memory-follows-the-operator), so they do not form a delivery group.
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.
Follows hq#342 (merged), from the independent review of mesh-catalog#276: design 36 §12 now says a project is one entry of the projects directory and a path is relative with no empty,
.or..part, and a value in the state naming anything else is never taken. ADR 0343 says the same in clause 1 through a progressive insight (version 15, under the knowledge base's review).sh merge-check.shpasses locally.Delivery
novox/hq@d70c189ed2ab— delivered since 2026-10-13T14:27:18ZDelivery 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.Verdict: approve at
d70c189ed2The added sentence in design 36 §12 says that a project is one entry of the projects directory and that a path is relative with no part empty,
.or.., and that a value naming anything else is never taken. That matchesNameProblemin mesh-catalog #276 at 305601d2 exactly. It is a safeguard on ADR 0343's clauses, not a new decision, so it belongs in the design. Role names only; mesh/repo-check passes.Not blocking: the edited line is longer than its neighbours, so rewrap it. #276 also adds a warning when a memory file cannot be written on a node. One sentence under §12's conflict row would record it, ideally in the same PR as the fix that makes it clear (see my review on #276).
Order: merge this before or together with mesh-catalog #276. The branch names differ (design/367-memory-names and fix/367-memory-follows-the-operator), so they do not form a delivery group.