Issue 609 (genesis stops at its store step: the bundle's store is not the postgres module's server). Decision: ADR 0338 (proposed, needs the operator), the store's twin of ADR 0333.
This gives ADR 0338 its home. To-be 17 adds ADR 0338 to decisions and one paragraph after the build agent's part. The paragraph says the bundle raises the store as the postgres module declares it: name, image, data directory and superuser password file. Every step reaches the store by that name, and the store step adopts it without a restart. It also says how this is checked. The paragraph uses no node names and no paths.
Checks run here: cycle.py, records.py, index.py and words.py pass, and merge-check.sh passes. updated is already today.
Issue 609 (genesis stops at its store step: the bundle's store is not the postgres module's server). Decision: ADR 0338 (proposed, needs the operator), the store's twin of ADR 0333.
This gives ADR 0338 its home. To-be 17 adds `ADR 0338` to `decisions` and one paragraph after the build agent's part. The paragraph says the bundle raises the store as the `postgres` module declares it: name, image, data directory and superuser password file. Every step reaches the store by that name, and the store step adopts it without a restart. It also says how this is checked. The paragraph uses no node names and no paths.
Checks run here: cycle.py, records.py, index.py and words.py pass, and merge-check.sh passes. `updated` is already today.
Deliverynovox/hq@6c8943d93453 — delivered since 2026-10-13T05:16:58Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-13 05:11 (new) → proposed (announced): novox/hq#338's head announced
2026-10-13 05:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 05:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 05:16 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 05:16 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@6c8943d93453` — **delivered** since 2026-10-13T05:16:58Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-13 05:11 (new) → proposed (announced): novox/hq#338's head announced
- 2026-10-13 05:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-13 05:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-13 05:16 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 05:16 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`.
I cloned novox/hq over HTTPS from git.novox.be into /var/tmp/review-hq338 at branch design/609-the-store-genesis-raises; its head is exactly 6c8943d934, matching the pull request's head sha.
The paragraph matches ADR 0338 and states nothing it does not decide. It covers clause 1 ("The genesis bundle takes the postgres module's layout... These are the names, image, path and file the module declares. The module does not change, so no running mesh's store moves."), clause 2 ("The installer and the bundle's steps address the store by that name."), clause 3 ("Adoption keeps the store as it runs... the store is not restarted at adoption."), and the first and last checks of clause 5. It correctly abstracts the manifest literals the ADR states (the container name, the pgvector image, /var/lib/mesh-store, 999:70, the superuser secret file) into "the name", "the image", "the data directory" and "the superuser password file" "that the catalogue's postgres module declares", matching AGENTS.md's "a manifest field may be named; a manifest may not be pasted." It omits clause 4 (the store port) and the two Consequences bullets that the ADR's own latest review flagged, rather than restating them. For context the operator should have: ADR 0338 is still "status": "proposed" with "needs-operator": true, and its most recent shown review (version 4, by "the agent on novox (sonnet)") returned "verdict": "changes", asking for a check on clause 4 and for the two Consequences bullets (the installer's refusal looking at /var/lib/mesh-store instead of the volume mesh-store-data, and the bundle's image pin moving with the module's pin) to be tied to a clause or removed. The design paragraph echoes neither, so it is unaffected by that open review, but the record itself still needs those fixed and the operator's approval before it is accepted.
The frontmatter is right: decisions gained "ADR 0338" and updated is set to 2026-10-13, today.
The diff follows the public-repo rule: no node names, hosts, usernames or absolute paths. It names only "the name", "the image", "the data directory" and "the superuser password file" the module declares, never the literal container name, image tag, /var/lib/mesh-store or 999:70 the ADR itself states. Those specifics are the postgres module's own manifest facts, true of any mesh running it, not something that teaches only this installation, so even stated they would need no role-phrasing — but the diff is right not to paste them regardless.
Glossary words check out: "store", "bundle", "module", "manifest", "catalogue" and "adopted" are used as 00-META/glossary.md defines them (store is "the one postgres server"; "the store is adopted where it runs" matches the glossary's adopted, "the mesh holds what it found there as found"). ./merge-check.sh passed all four checks, exit code 0: "records: all checks passed"; "index: 6 topics in the reading order, no stored list" (its "NOT COMPARED" note is only because MESH_CATALOG_DIR was unset locally, not a failure); "cycle: 436 documents checked, the chain holds"; "words: 28 retired words and 2 identifiers, none in running prose; 70 daemons' lines, none written; 155 head words, each once".
Verdict: approve at 6c8943d93453185ef4734f7099809d53b5238344
I cloned novox/hq over HTTPS from git.novox.be into /var/tmp/review-hq338 at branch design/609-the-store-genesis-raises; its head is exactly 6c8943d93453185ef4734f7099809d53b5238344, matching the pull request's head sha.
1. The paragraph matches ADR 0338 and states nothing it does not decide. It covers clause 1 ("The genesis bundle takes the postgres module's layout... These are the names, image, path and file the module declares. The module does not change, so no running mesh's store moves."), clause 2 ("The installer and the bundle's steps address the store by that name."), clause 3 ("Adoption keeps the store as it runs... the store is not restarted at adoption."), and the first and last checks of clause 5. It correctly abstracts the manifest literals the ADR states (the container name, the pgvector image, `/var/lib/mesh-store`, `999:70`, the `superuser` secret file) into "the name", "the image", "the data directory" and "the superuser password file" "that the catalogue's postgres module declares", matching AGENTS.md's "a manifest field may be named; a manifest may not be pasted." It omits clause 4 (the store port) and the two Consequences bullets that the ADR's own latest review flagged, rather than restating them. For context the operator should have: ADR 0338 is still `"status": "proposed"` with `"needs-operator": true`, and its most recent shown review (version 4, by "the agent on novox (sonnet)") returned `"verdict": "changes"`, asking for a check on clause 4 and for the two Consequences bullets (the installer's refusal looking at `/var/lib/mesh-store` instead of the volume `mesh-store-data`, and the bundle's image pin moving with the module's pin) to be tied to a clause or removed. The design paragraph echoes neither, so it is unaffected by that open review, but the record itself still needs those fixed and the operator's approval before it is accepted.
2. The frontmatter is right: `decisions` gained `"ADR 0338"` and `updated` is set to `2026-10-13`, today.
3. The diff follows the public-repo rule: no node names, hosts, usernames or absolute paths. It names only "the name", "the image", "the data directory" and "the superuser password file" the module declares, never the literal container name, image tag, `/var/lib/mesh-store` or `999:70` the ADR itself states. Those specifics are the postgres module's own manifest facts, true of any mesh running it, not something that teaches only this installation, so even stated they would need no role-phrasing — but the diff is right not to paste them regardless.
4. Glossary words check out: "store", "bundle", "module", "manifest", "catalogue" and "adopted" are used as 00-META/glossary.md defines them (store is "the one postgres server"; "the store is adopted where it runs" matches the glossary's adopted, "the mesh holds what it found there as found"). `./merge-check.sh` passed all four checks, exit code 0: "records: all checks passed"; "index: 6 topics in the reading order, no stored list" (its "NOT COMPARED" note is only because `MESH_CATALOG_DIR` was unset locally, not a failure); "cycle: 436 documents checked, the chain holds"; "words: 28 retired words and 2 identifiers, none in running prose; 70 daemons' lines, none written; 155 head words, each once".
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.
Issue 609 (genesis stops at its store step: the bundle's store is not the postgres module's server). Decision: ADR 0338 (proposed, needs the operator), the store's twin of ADR 0333.
This gives ADR 0338 its home. To-be 17 adds
ADR 0338todecisionsand one paragraph after the build agent's part. The paragraph says the bundle raises the store as thepostgresmodule declares it: name, image, data directory and superuser password file. Every step reaches the store by that name, and the store step adopts it without a restart. It also says how this is checked. The paragraph uses no node names and no paths.Checks run here: cycle.py, records.py, index.py and words.py pass, and merge-check.sh passes.
updatedis already today.Delivery
novox/hq@6c8943d93453— delivered since 2026-10-13T05:16:58ZDelivery 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
6c8943d934I cloned novox/hq over HTTPS from git.novox.be into /var/tmp/review-hq338 at branch design/609-the-store-genesis-raises; its head is exactly
6c8943d934, matching the pull request's head sha.The paragraph matches ADR 0338 and states nothing it does not decide. It covers clause 1 ("The genesis bundle takes the postgres module's layout... These are the names, image, path and file the module declares. The module does not change, so no running mesh's store moves."), clause 2 ("The installer and the bundle's steps address the store by that name."), clause 3 ("Adoption keeps the store as it runs... the store is not restarted at adoption."), and the first and last checks of clause 5. It correctly abstracts the manifest literals the ADR states (the container name, the pgvector image,
/var/lib/mesh-store,999:70, thesuperusersecret file) into "the name", "the image", "the data directory" and "the superuser password file" "that the catalogue's postgres module declares", matching AGENTS.md's "a manifest field may be named; a manifest may not be pasted." It omits clause 4 (the store port) and the two Consequences bullets that the ADR's own latest review flagged, rather than restating them. For context the operator should have: ADR 0338 is still"status": "proposed"with"needs-operator": true, and its most recent shown review (version 4, by "the agent on novox (sonnet)") returned"verdict": "changes", asking for a check on clause 4 and for the two Consequences bullets (the installer's refusal looking at/var/lib/mesh-storeinstead of the volumemesh-store-data, and the bundle's image pin moving with the module's pin) to be tied to a clause or removed. The design paragraph echoes neither, so it is unaffected by that open review, but the record itself still needs those fixed and the operator's approval before it is accepted.The frontmatter is right:
decisionsgained"ADR 0338"andupdatedis set to2026-10-13, today.The diff follows the public-repo rule: no node names, hosts, usernames or absolute paths. It names only "the name", "the image", "the data directory" and "the superuser password file" the module declares, never the literal container name, image tag,
/var/lib/mesh-storeor999:70the ADR itself states. Those specifics are the postgres module's own manifest facts, true of any mesh running it, not something that teaches only this installation, so even stated they would need no role-phrasing — but the diff is right not to paste them regardless.Glossary words check out: "store", "bundle", "module", "manifest", "catalogue" and "adopted" are used as 00-META/glossary.md defines them (store is "the one postgres server"; "the store is adopted where it runs" matches the glossary's adopted, "the mesh holds what it found there as found").
./merge-check.shpassed all four checks, exit code 0: "records: all checks passed"; "index: 6 topics in the reading order, no stored list" (its "NOT COMPARED" note is only becauseMESH_CATALOG_DIRwas unset locally, not a failure); "cycle: 436 documents checked, the chain holds"; "words: 28 retired words and 2 identifiers, none in running prose; 70 daemons' lines, none written; 155 head words, each once".