Demo Mode ActiveSynthetic portfolio data for evaluation. Metrics, pilot clients, and completion rates are strictly demonstrative simulations.

System Architecture, Supabase Auth & Cloud Persistence

Administrator authentication, Row-Level Security verification, explicit cloud synchronization, and local disaster recovery.

Storage Engine State: Device-Local Storage Onlylocal-only

Local browser storage active.

Administrator Cloud Authentication

All 12 portfolio tables are protected by strict PostgreSQL Row-Level Security. You must authenticate with the credentials registered in public.portfolio_admins to access cloud data.

Supabase Credentials Not Yet Configured in .env.local

To connect your cloud database, copy your dedicated project credentials into .env.local as shown in the integration guide below.

Explicit Cloud Migration & Sync

We never silently overwrite cloud data or upload local data automatically. Review the diff preview below before committing local records to the Supabase database.

Local Device Initiatives:5 records
Local Sprint Tasks & Blockers:5 items
Local Intelligence Reports:0 records
* Sign in as a verified administrator above to unlock cloud synchronization.

Storage Engine Diagnostics

Adapter TypeDevice-Local Storage
Schema Versionv2.0.0 (Persistent State)
Active Projects In Memory5 initiatives
Stored Tasks & Blockers5 items
Imported Intelligence Reports0 records

Backup & Disaster Recovery

Save your entire portfolio state to a portable JSON backup file or restore previously saved records.

Dedicated Supabase Project Configuration Guide

Where to find your publishable project credentials in the Supabase Dashboard.

Supabase Dashboard Instructions:

1. Go to your dedicated Project Status project at supabase.com/dashboard.

2. Navigate to Project Settings $\rightarrow$ API:

  • Copy Project URL into NEXT_PUBLIC_SUPABASE_URL.
  • Copy anon / public key into NEXT_PUBLIC_SUPABASE_ANON_KEY.

3. Security Rule: Never set or expose the service_role key in .env.local or any client code. PostgREST authorization is secured via Row-Level Security and public.portfolio_admins.