GAB Supabase Estate Consolidation — Two Applications, One Database

Advance analysis and reversible preparation. Production cutovers and each irreversible exact-ref project deletion remain subject to backup/restore evidence, G1/G2 authorization and explicit HITL retirement approvals.

The financial case is directional until a full post-cutover invoice. No data deletion before independent export and restore verification; no farm demo record may be treated as verified operational truth.

Authorize reversible delivery, inventory, backup work and tested cutovers. Gate 0 backup artifacts+restore are mandatory before any irreversible retirement. Each Supabase deletion and outward domain change requires separate exact-target Daniel/HITL decision. Stop on RLS exposure, lost/duplicated leads, false-current farm data or red production deploy.

Reversible engineering and migration preparation may execute. Live data cutovers require verified independent backup and restore, source/destination reconciliation, RLS/security checks and tested rollback. Supabase project deletion and public-domain changes remain separate exact-target CEO/HITL decisions. No new paid add-on or schedule/cost commitment is implied.

CEO need (2026-10-05): stop paying compute for seven independent Supabase projects that arose from historical experimentation. Future state: one GAB OS Supabase database while retaining separate GAB OS and public website applications. Farm ERP was intended as daily staff data capture but was not adopted; its demonstration records are not verified farm history. Website records and live routes must survive. Evidence: invoice NOTQHR-00011 ($82.74), live project inventory and source-code dependency audit, GAB OS Farm/Website contracts, and backup alert 05865976-3404-42a0-bc9e-fd711d44ee46. Strategic alignment: GOV operational discipline, AGRI evidence-first farm operations, GIST source truth; ne

Do nothing: continue paying roughly $82.74 for the last invoice pattern, including compute on dormant projects, and preserve split-data complexity. Preferred: retain two deployments/repositories but one GAB OS Supabase project, migrate website receipts/content and supported Farm Agent functions, archive demonstrations, retire redundant paid projects in approved waves. A one-Micro-project steady state is expected to be near the $25 Pro base while within the organization's $10 monthly compute credit and other included quotas; this is a hypothesis to verify on a full-cycle invoice, not a guaranteed price. Nonfinancial value: simpler data ownership, fewer cross-project credentials and sync failu

Benefits: (1) six redundant paid Supabase projects retired, leaving GAB OS as sole active paid project; measure via live project list and invoice. (2) Public website and GAB OS remain independently deployable and healthy; measure on production routes and release checks. (3) Website inquiries, content, resources, leads and owned response workflow preserved without duplicate/missing records; measure record reconciliation and live submission. (4) Farm Agent no longer depends on an unused ERP DB or presents demo rows as field truth; measure tool/dashboard/cron tests and fresh-source claims. (5) Verified independent backups and restore drills; measure artifacts and restored records. Review after

Purpose: implement the approved two-app/one-database architecture. Scope: current Supabase dependency inventory; independent export and restore tests; retire dormant demo/original projects after explicit per-ref approval; repoint Farm Agent/website integrations; move website data and server-side workflows into GAB OS Supabase with safe Auth/RLS/Edge Function treatment; update contracts, migrations, tests, secrets, runbooks and billing verification. Out of scope: redesigning website/GAB OS, importing unverified ERP data as farm history, inventing a Finance banking subsystem, deleting code/history, changing public domains without separate HITL. Owner: Daniel Nsowah. Delivery gate: every irreve

Wave 0 verified independent backup and restore; Wave 1 archive and separately approve dormant projects; Wave 2 Farm Agent cutover with truthful data provenance and ERP rollback window; Wave 3 website database migration with preserved IDs/intake idempotence, live form/content tests, and old DB rollback window; Wave 4 exact-ref retirement and full billing-cycle check. Stop on missing backup, failed data reconciliation, RLS/auth exposure, broken form/email, false farm claims, or red deployment. See docs/projects/2026-10-05_supabase-estate-consolidation-plan.md.

Wave 0 verified independent backup and restore; Wave 1 archive and separately approve dormant projects; Wave 2 Farm Agent cutover with truthful data provenance and ERP rollback window; Wave 3 website database migration with preserved IDs/intake idempotence, live form/content tests, and old DB rollback window; Wave 4 exact-ref retirement and full billing-cycle check. Stop on missing backup, failed data reconciliation, RLS/auth exposure, broken form/email, false farm claims, or red deployment. See docs/projects/2026-10-05_supabase-estate-consolidation-plan.md.