coulomb/tenant-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Implement PostgreSQL production store path
All checks were successful
Build and Publish Container Image / build-and-push (push) Successful in 41s
Details

Browse source 
Add the PostgreSQL backend, migration and stopped-write transfer tools, lease-aware deployment manifests, tenancy declarations, and shared conformance coverage. Persist grouping mutations in durable stores and separate process liveness from database readiness.
This commit is contained in:
tegwick 2026-08-19 14:42:01 +02:00
parent 2063470ac8
commit 749461b97b
30 changed files with 2364 additions and 71 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/tenant-lifecycle-api.md
View file

@ -35,6 +35,11 @@ Reactivation restores the tenant's ability to receive new grants and plan
changes. It deliberately does **not** resurrect revoked grants or invent plan
state — those stay exactly as retirement left them.
Retention and erasure semantics are normative in
`docs/data-retention-policy.md`. In particular, retirement does not erase
contact data, and the 30-day PostgreSQL backup window is a copy horizon rather
than a primary-record expiry rule.
---
## Immutability