Ozuaa
Launch Blockers

Public preview is ready. Commercial production still needs approval.

This page keeps the final production blockers visible while the Ozuaa ecosystem remains available for public-preview exploration.

Preview Readiness

99%

Static public preview, launch evidence, founder decision templates, staging backend task breakdown, RLS test plan, Supabase seed mapping, read-only adapter plan, waitlist staging activation plan, production blocker summaries, release lock, stakeholder walkthrough, staging approval index, and founder handoff summary are in place.

Production Status

Blocked

Production requires real Supabase, auth, legal, support, monitoring, payment, escrow, logistics, and domain approvals.

Next Unblock

Approve protected staging, complete the staging intake, and provide Supabase staging inputs before backend-backed implementation begins.

Open launch center

Founder Inputs

Supabase project values, auth policy, waitlist destination, support identity, legal approvals, provider choices, and DNS access remain required.

Review contact readiness

Approval Reviews

Auth/role approval and waitlist destination review are now separated so staging can begin without accidentally implying commercial launch.

Review public status

Supabase Preflight

Supabase staging variables can exist in Vercel now, but the app still uses seeded data until the staging backend sequence is approved.

Open launch center

Migration Safety

Schema and RLS drafts must pass dry-run checks, role approval, seeded test mapping, read-only adapter review, and waitlist consent review before staging apply.

Review status

Staging Readiness Gates

RLS test evidence, Supabase seed mapping, read-only adapter approval, and waitlist staging consent must be completed before live backend behavior is enabled.

Open launch center

Evidence Capture

Supabase staging evidence must show required variable names, disabled adapters, no printed secrets, and blocked production status before backend work continues.

Review status

RLS Evidence

Staging policy work must produce positive and negative role-test evidence before Supabase reads, writes, or waitlist capture are activated.

Open launch center

Seed Evidence

Synthetic staging seed data is prepared for review only; production data, real contacts, and waitlist inserts remain blocked.

Review status

Adapter Prototype

The Supabase read-only adapter remains disabled and catalog-scoped until staging evidence, RLS proof, and owner approval are complete.

Open launch center

Fallback Evidence

Seeded static fallback must remain active for failed, denied, empty, or mismatched Supabase reads until staging review is approved.

Review status

Waitlist Write Prototype

Waitlist staging writes remain disabled until consent copy, privacy policy, destination owner, deletion process, and RLS evidence are approved.

Review waitlist