Gives ADR 0343 (proposed in the knowledge base, needs the operator's Approve) its home in design 36, for issue 367 (a session's memory stays on the node where it was learned).
New §12: the module carries each project's memory folder and nothing else of the home: how a change is picked up, carried, merged on a conflict (both kept, newer first, a warning through notify), removed (a marker; a change outlives it; a missing folder or lost key removes nothing), the first carrying, the read-only tool, the two home kinds kept apart, no tool writes memory (issue 340), and the gap tracked by issue 638.
§10's list of working state notes that the memory folders are now also carried.
Two rows in "How it is checked".
decisions: gains ADR 0343, updated: 2026-10-13.
Checks run locally: sh merge-check.sh (records, index, cycle, words) passes.
Gives ADR 0343 (proposed in the knowledge base, needs the operator's Approve) its home in design 36, for issue 367 (a session's memory stays on the node where it was learned).
- New §12: the module carries each project's memory folder and nothing else of the home: how a change is picked up, carried, merged on a conflict (both kept, newer first, a warning through `notify`), removed (a marker; a change outlives it; a missing folder or lost key removes nothing), the first carrying, the read-only tool, the two home kinds kept apart, no tool writes memory (issue 340), and the gap tracked by issue 638.
- §10's list of working state notes that the memory folders are now also carried.
- Two rows in "How it is checked".
- `decisions:` gains ADR 0343, `updated:` 2026-10-13.
Checks run locally: `sh merge-check.sh` (records, index, cycle, words) passes.
Code: novox/mesh-catalog#276.
Deliverynovox/hq@319c2106246e — delivered since 2026-10-13T14:14:39Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 14:05 (new) → proposed (announced): novox/hq#342's head announced
2026-10-13 14:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 14:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 14:14 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:14 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@319c2106246e` — **delivered** since 2026-10-13T14:14:39Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 14:05 (new) → proposed (announced): novox/hq#342's head announced
- 2026-10-13 14:06 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 14:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 14:14 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:14 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`.
Independent review for issue 367 against ADR 0343 (version 14). Design 36 §12 states clauses 1, 2, 4, 5, 6, 7, 8, 9, 10, 11 and 12 faithfully and adds nothing the record does not decide. The frontmatter names ADR 0343 and the date moves to 2026-10-13. The exception added to the working-state list (around line 406) is correct. The text uses role names only (the laptop, the workstation), no node names, paths or addresses. mesh/repo-check passes (records, index, cycle, words).
Not blocking:
The new line around 406 is not wrapped like its neighbours.
The "How it is checked" row for the module's tests lists fewer cases than ADR 0343 clause 13. It leaves out a node that was away taking the newest version, two versions too large for one file, a text too large once encoded, a password in an address refused while a commit hash is carried, and every replaced version being in memory-copies/. Consider naming them all.
The companion code PR, mesh-catalog #276, has a request-changes review: a project name taken from the state is not checked, unscreened local text can reach the state, and a read failure is carried as a removal. If the fix adds the rule that a project and path from the state must name one folder entry and a relative path inside it, one sentence here under "No tool writes memory" would record it.
Order: merge this PR before mesh-catalog #276, so the design names ADR 0343 before the code that builds it ships. The two branch names differ, so they do not form a delivery group.
Verdict: approve at 319c2106246e652f3a0baefc4dbb538b888de55e
Independent review for issue 367 against ADR 0343 (version 14). Design 36 §12 states clauses 1, 2, 4, 5, 6, 7, 8, 9, 10, 11 and 12 faithfully and adds nothing the record does not decide. The frontmatter names ADR 0343 and the date moves to 2026-10-13. The exception added to the working-state list (around line 406) is correct. The text uses role names only (the laptop, the workstation), no node names, paths or addresses. mesh/repo-check passes (records, index, cycle, words).
Not blocking:
- The new line around 406 is not wrapped like its neighbours.
- The "How it is checked" row for the module's tests lists fewer cases than ADR 0343 clause 13. It leaves out a node that was away taking the newest version, two versions too large for one file, a text too large once encoded, a password in an address refused while a commit hash is carried, and every replaced version being in `memory-copies/`. Consider naming them all.
- The companion code PR, mesh-catalog #276, has a request-changes review: a project name taken from the state is not checked, unscreened local text can reach the state, and a read failure is carried as a removal. If the fix adds the rule that a project and path from the state must name one folder entry and a relative path inside it, one sentence here under "No tool writes memory" would record it.
Order: merge this PR before mesh-catalog #276, so the design names ADR 0343 before the code that builds it ships. The two branch names differ, 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.
Gives ADR 0343 (proposed in the knowledge base, needs the operator's Approve) its home in design 36, for issue 367 (a session's memory stays on the node where it was learned).
notify), removed (a marker; a change outlives it; a missing folder or lost key removes nothing), the first carrying, the read-only tool, the two home kinds kept apart, no tool writes memory (issue 340), and the gap tracked by issue 638.decisions:gains ADR 0343,updated:2026-10-13.Checks run locally:
sh merge-check.sh(records, index, cycle, words) passes.Code: novox/mesh-catalog#276.
Delivery
novox/hq@319c2106246e— delivered since 2026-10-13T14:14:39ZDelivery 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
319c210624Independent review for issue 367 against ADR 0343 (version 14). Design 36 §12 states clauses 1, 2, 4, 5, 6, 7, 8, 9, 10, 11 and 12 faithfully and adds nothing the record does not decide. The frontmatter names ADR 0343 and the date moves to 2026-10-13. The exception added to the working-state list (around line 406) is correct. The text uses role names only (the laptop, the workstation), no node names, paths or addresses. mesh/repo-check passes (records, index, cycle, words).
Not blocking:
memory-copies/. Consider naming them all.Order: merge this PR before mesh-catalog #276, so the design names ADR 0343 before the code that builds it ships. The two branch names differ, so they do not form a delivery group.