Environment separation
- Dedicated production Supabase project
- Separate staging/test project
- No risky production testing
v172 backend track
Supabase global deployment readiness.
This page keeps the database scale track visible for Terra Vita Hub. v172 adds the SQL hardening pack, runbook, risk-assurance register, export audit log, sovereignty configuration, background-job queue, continuity checks, MRV quality checks, conditional indexes, and readiness views required before global deployment.
Operational boundary: this ZIP does not change the live Supabase database. Run the SQL in staging first, validate role access and page behaviour, then promote to production through a controlled migration.
Access & RLS
- RLS audit view
- Admin helper function
- Programme, organisation, and user boundaries to test
Performance
- Conditional indexes for high-use tables
- Connection pooling review
- Load-test control register
Background processing
- Queue table for AI Advice, exports, satellite, and TV-CRI
- Job event logging
- Retry and status tracking
Governance & assurance
- Risk-assurance register
- Data-export audit log
- Data-sovereignty configuration
Continuity
- Backup/PITR control
- Restore drill register
- Incident response and continuity route
Global readiness rule
The database should not be treated as global-ready until all critical controls in public.global_deployment_controls are marked ready, or formally accepted as risk by the authorised governance owner.