From 43f356561707bce3995deb5f1bd8da648b3f0769 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 16 Sep 2026 21:20:00 +0200 Subject: [PATCH] =?UTF-8?q?WBS:=20correct=203.1=20phrasing=20=E2=80=94=20a?= =?UTF-8?q?=20module=20gets=20a=20database=20only=20if=20it=20asks?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Not "every module's database"; modules request one via requires postgres-database. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx --- 03-DESIGN/01-to-be/22-the-work-ahead.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/22-the-work-ahead.md b/03-DESIGN/01-to-be/22-the-work-ahead.md index ff0d50f..ec7df41 100644 --- a/03-DESIGN/01-to-be/22-the-work-ahead.md +++ b/03-DESIGN/01-to-be/22-the-work-ahead.md @@ -80,7 +80,7 @@ raises gitea and publishes the SDK before the base build. Those close together i a protocol that agrees, a registry to publish to. Issue 051. - [x] 3.1 the store is adopted — raised at genesis, then held as the `postgres` module; one server, - the controller's records and every module's database in it. *(Adopted in place: the module's + the controller's records and the database of each module that asks for one. *(Adopted in place: the module's server names the same container and the same pinned upstream image the foundation runs, so the applier reconciles it rather than raising a second postgres. Proven 22/22 in the one-node lab — the catalogue, a `postgres-database` consumer, gets its database from it. Follow-up: the store