Production Cutover Command Center
Dwellmark production readiness
A secret-safe launch cockpit for Vercel, Supabase, private storage, tenant boundaries, advisor access, privacy controls, production smoke, demo-mode separation, and billing deferral.
Next Action
Production cutover cockpit is ready for controlled account rollout; billing can remain deferred.
No secret values are returned by this endpoint.
Production Service Cutover
Production service namespace is ready for controlled authenticated cutover; keep demo routes separate.
/api/dashboard
Demo: /api/dashboard/demo/api/ledger/days
Demo: /api/ledger/demo/days/api/ledger/corrections
Production-only route/api/evidence/vault/records
Production-only route/api/evidence/vault/uploads
Production-only route/api/evidence/vault/uploads/complete
Production-only route/api/evidence/vault/downloads
Production-only route/api/evidence/vault/downloads/by-record
Production-only route/api/evidence/readiness
Production-only route/api/mobile/capture
Demo: /api/mobile/demo/capture/api/operations
Demo: /api/operations/demo/api/operations/readiness
Demo: /api/operations/readiness/demo/api/advisor/issue-queue
Demo: /api/advisor/demo/issue-queue/api/advisor/readiness
Production-only route/api/privacy/controls
Demo: /api/privacy/demo/controls/api/privacy/readiness
Production-only route/api/auth/bootstrap
Production-only route/api/auth/session
Production-only route/api/advisor/invites
Production-only route/api/advisor/invites/accept
Production-only route/api/household/members
Production-only route/api/validation/readiness
Demo: /api/validation/demo/readiness/api/launch/readiness
Demo: /api/launch/readiness/demo/api/audit-packet
Demo: /api/audit-packet/demo/api/audit-packet/files
Production-only route/api/audit-packet/files/[artifact]
Demo: /api/audit-packet/demo/files/[artifact]/api/annual-review
Production-only route/api/launch/readiness
Demo: /api/launch/readiness/demo/api/launch/operations
Production-only route/api/trust/readiness
Production-only route/api/jurisdictions/readiness
Production-only route/api/beta/offers
Production-only routePhase 6 Evidence
Production service replacement checklist
32 production routes are inventoried with explicit demo boundaries and secret-safe responses.
/api/dashboard is database-backed, bearer-session gated, tenant-scoped, and separated from /api/dashboard/demo.
/api/evidence/vault routes cover inventory, signed upload URLs, upload completion, signed downloads, and record-backed downloads through private Storage.
/api/ledger/days and /api/ledger/corrections cover read rows plus audited correction writes.
/api/advisor/issue-queue is production-backed, tenant-scoped, audited, and demo-separated.
/api/privacy/controls, /api/auth/bootstrap, /api/auth/session, advisor invites, invite acceptance, and household member inventory/onboarding cover the auth cutover boundary.
/api/audit-packet, packet file routes, and /api/annual-review cover export records, private artifact URLs, and annual closeout readiness.
/api/backend/production-readiness exposes environment, Supabase, route, tenant, storage, audit, demo, and secret-safe evidence.
Committed Supabase migrations define household isolation policies with authenticated scope, write with-check protection, and live policy inventory smoke coverage.
Auth Cutover
Owner, household, and advisor onboarding readiness
Supabase Auth is reachable for email/password, magic-link, owner, household member, and advisor session verification.
/api/auth/bootstrap creates encrypted user, household membership, auth-session, and audit records.
/api/auth/session verifies bearer sessions and returns tenant scope without emails, tokens, or encrypted receipts.
/api/advisor/invites creates, updates, and revokes encrypted advisor invites with audit receipts.
/api/advisor/invites/accept binds an authenticated advisor to an unexpired invite and records encrypted session receipts.
/api/household/members lets owner/member sessions review household membership and lets owners add encrypted household member profiles and membership records.
Public design-review routes remain no-auth and separate from authenticated production account routes.
Account Rollout Plan
Controlled accounts before billing or broad login
Run owner, household, advisor, private-evidence, and public-demo rehearsal before enabling real user accounts.
Owner bootstrap, session probe, tenant access, dashboard, ledger, evidence, privacy, advisor, and packet probes pass without rendering secrets.
owner · /production-appOwner-scoped household member creation is encrypted, tenant-scoped, audited, and excluded from public review routes.
household · /api/household/membersAdvisor invite create, update, revoke, acceptance, queue access, redaction, and audit receipts are verified.
advisor · /api/advisor/invitesPrivate upload, authorized download, signed packet artifacts, cross-household denial, audit events, and retention controls are captured privately.
operations · docs/PRODUCTION_CUTOVER_REHEARSAL.mdHomepage, owner command center, design handoff, prototype, sitemap, robots, and llms routes remain no-auth and demo-safe.
public-demo · /Deferred until after controlled rollout
Billing and checkout, Advisor firm tenancy, Concierge fulfillment automation, Production mobile background uploads
Cutover Rehearsal
Manual evidence required before real user accounts
Launch remains blocked until every rehearsal item has current private evidence, verifier commands are green, and public demo/design routes remain no-auth.
Upload one non-sensitive test evidence file, complete the upload, and confirm the evidence inventory shows the record.
evidence · private evidence locationRequest a short-lived signed download URL for the test record and confirm the authorized household can access it.
evidence · private evidence locationConfirm a different household or session cannot read or sign the evidence object.
evidence · private evidence locationGenerate a test packet and confirm manifest, attestation, PDF, and ZIP artifacts are written to private packet storage.
packet · private evidence locationRequest short-lived signed URLs for each packet artifact and confirm the URLs expire according to the configured TTL.
packet · private evidence locationAttempt same-table reads and writes from another household and confirm tenant isolation blocks access.
rls · private evidence locationConfirm an advisor without explicit exact-location permission cannot view exact location or private evidence objects.
advisor · private evidence locationConfirm platform audit events record auth, advisor, evidence, correction, export, and delete activity.
audit · private evidence locationConfirm export and delete requests respect retention review before any deletion confirmation.
retention · private evidence locationdocs/PRODUCTION_CUTOVER_REHEARSAL.md
No secrets, signed URLs, raw evidence files, exact-location records, database URLs, passwords, tokens, or service-role keys are returned by this endpoint.
Production environment
readyRequired Vercel and Supabase environment values are present and secret-safe.
Keep production variables scoped to the correct Vercel environment.Production API coverage
readyAuthenticated production API routes exist beside demo routes.
Keep demo routes separate from production routes.Supabase Auth
readySupabase Auth is reachable for session bootstrap.
Proceed with controlled auth UI wiring after UX approval.Supabase database contract
readyRequired tenant-scoped tables are reachable through Supabase REST.
Keep migrations as the source of truth.Private storage
readyEvidence and packet storage buckets are private and reachable.
Use signed upload and download flows for production evidence.Tenant and advisor access
readytenant access ready; advisor access ready
Keep owner, household, and advisor access explicitly scoped.Privacy and redaction
readyExact-location redaction, encrypted sensitive fields, and data controls are represented.
Keep exact location hidden by default in advisor flows.Production smoke
readyProduction readiness smoke can validate the deployed endpoint without exposing secrets.
Keep smoke checks in the release gate.Demo mode boundary
readyPublic demo/design mode remains separate from authenticated production routes.
Preserve demo mode after login is added.Billing
deferredBilling remains deferred; paid-beta packaging can be reviewed without real checkout.
Keep real checkout disabled until paid-beta packaging is approved.Readiness checks
ready11 required environment variable(s) are configured.
App, Supabase, and database URL values are well formed.
This deployment is not a Vercel Preview environment.
Supabase Auth settings endpoint is reachable.
2 expected private Dwellmark bucket(s) are configured.
4 private Storage object polic(ies) are installed.
14 required table(s) are reachable through Supabase REST.
2 storage policy row(s), 6 sensitive field row(s), and 8 audit capture(s) are ready.
10 committed migration version(s) are present in remote Supabase history.
14 household isolation polic(ies) are installed.
Cutover guardrails
guarded- Billing remains deferred until paid-beta checkout is approved.
- Public demo and design-review routes remain separate from production account routes.
- Server-only secrets are checked without returning secret values.
- Exact-location and advisor access boundaries stay part of the launch gate.
Ready posture
All active production checks are ready. Billing can remain deferred while controlled account rollout begins.
Launch Evidence Manifest
Production smoke and manual evidence index
The launch evidence manifest at /api/launch/evidence/manifest exposes evidenceSourceSummary and automatedSmokeEvidence blocks for production promotion. Reviewers should confirm manual evidence buckets, required production smoke surfaces, demo readiness surfaces, live readiness surfaces, secret-policy checks, launch approval boundaries, and evidence-source reconciliation before accepting launch evidence. The launchApprovalChecklist must show external-provider-evidence, live-supabase-smoke, production-readiness-smoke, and manual-cutover-review before real users are enabled.
- Seeded demo readiness is not production launch approval.
- Manual evidence remains required for external provider, browser-session, and local-command gates.
- Production smoke must validate secret policy, launch approval boundaries, and manifest reconciliation.