Merge pull request 'To-be 17: the store genesis raises is the postgres module's server (issue 609, ADR 0338)' (#338) from design/609-the-store-genesis-raises into main

03-DESIGN/01-to-be/17-raising-a-mesh.md

@@ -17,6 +17,7 @@ decisions:
   - "ADR 0010"
   - "ADR 0036"
   - "ADR 0336"
+  - "ADR 0338"
 ---
 
 # Raising a mesh
@@ -169,6 +170,15 @@ names the gitea module as what provides it. It never builds without the credenti
 mesh's scope from the public registry. Go artifacts, images that do not name `.npmrc` and upstream images
 need no registry. The gitea module's own server is an upstream image, so building the forge needs no forge.
 
+**The store genesis raises is the `postgres` module's server, so adopting it keeps it** (ADR 0338, the
+store's twin of the bus's ADR 0333). The bundle raises the store under the name, on the image, in the data
+directory and with the superuser password file that the catalogue's `postgres` module declares, and every step
+of the bundle and of the installer reaches it by that name. At the store step the module declares the
+container the bundle raised, so the store is adopted where it runs and is not restarted. The module does not
+change, so no running mesh's store moves. *How it is checked:* a test reads the module's manifest and holds
+the bundle to it, the module's image is measured initialising a new store on a data directory made as the
+bundle makes it, and the bed that raises genesis from bare passes the store step and reaches the broker step.
+
 **The core modules are built.** Each is named by a repository and a path
 (ADR 0069), and the builder is
 asked for each in turn: it clones, reads the manifest at that path, produces what it declares,