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

This commit is contained in:
2026-10-13 16:20:14 +02:00
parent e7ebafad1a
commit d70c189ed2
@@ -526,7 +526,9 @@ asker's subjects and its own records there.
*Added 2026-10-13 by ADR 0343 (issue 367).*
A session started on another node starts with what the sessions on every other node learned. **The module
carries each project's memory folder**, `~/.claude/projects/<project>/memory/`, and nothing else of the home.
carries each project's memory folder**, `~/.claude/projects/<project>/memory/`, and nothing else of the home. A project is
one entry of the projects directory and a path is relative, no part of it empty, `.` or `..`: a value in the state
naming anything else is never taken, and nothing is touched for it.
| Step | What happens |
|---|---|