Design 36 §12: the names a memory value may carry (issue 367, ADR 0343) #343

Merged
mesh-admin merged 1 commits from design/367-memory-names into main 2026-10-13 14:26:55 +00:00
Contributor

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.
mesh-admin added 1 commit 2026-10-13 14:20:19 +00:00
Design 36 §12: say which project and path names a memory value may carry (issue 367, ADR 0343)
mesh/merge-gate head d70c189ed2ab merged into trunk e7ebafad1aa9 — pass: the change touches no module of the mesh's graph
mesh/repo-check head d70c189ed2ab merged into trunk e7ebafad1aa9 — pass: its merge-check.sh passed
mesh/delivery delivered
d70c189ed2
Author
Contributor

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.

<!-- 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`.
mesh-admin left a comment
Author
Contributor

Verdict: approve at d70c189ed2

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.
mesh-admin merged commit 471f99344b into main 2026-10-13 14:26:55 +00:00
mesh-admin deleted branch design/367-memory-names 2026-10-13 14:26:56 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#343