feat: P3 effective configuration, memory root, and revision-scoped records

2026-08-12 16:01:25 +02:00
parent beaba548c1
commit e23e526966
21 changed files with 1108 additions and 44 deletions
@@ -25,6 +25,15 @@ per `docs/contracts/workspace-preprocessing-cli.md` and the P2 walkthrough in
 `workspace-maintenance` Compose service; it never starts a backend/Pi/frontend listener and never
 attaches Git credentials.

+
+## Effective configuration and `.tht-dwh` (P3)
+
+Prepared DWH generations are reusable and safe: `thothctl` and the application derive the same
+canonical effective configuration and logical identity, so prepared work is reused when nothing
+relevant changed and refused when the database/endpoint/identity changed. See
+`docs/contracts/tht-dwh.md` for generations, `OWNER.json`, `ACTIVE`, fingerprints, migration and
+recovery. A content-only or Evidence-only change never forces a full re-introspection.
+
 ## Service account, storage, and firewall

 Create a dedicated host service account and an operator root such as `/srv/thothii`. The core