Launch readiness

AIRCITE customer-live gate

A public, sanitized launch-status surface for the blockers that must clear before AIRCITE can be opened for customer use.

Live contract

Readiness comes from /api/health

This page renders the same sanitized health contract used by the app shell. It can show blockers and booleans, but it never returns token values, tenant payloads, customer records, PHI, or secret values.

LIVE

Launch readiness

Sanitized customer-live checklist from /api/health. This panel shows what is ready and what is still blocked without returning secret values, tenant records, domains from private data, or PHI.

Customer-live gateAll launch checks must be ready before customer-use sign-off
Blocked
Health response/api/health runtime contract
...
Evidence boundaryNo PHI and no secret values returned
Pending
Marketing domainNeeds aircite.ai/www.aircite.ai public-domain proof.
Blocked
Customer app domainNeeds app.aircite.ai DNS and alias proof: No missing items reported.
Blocked
Environment configRequired public and server env keys are present. Secret values are never returned.
Ready
Tenant accessNeeds Supabase public anon config plus tenant-gate runtime proof with a browser session.
Blocked
Analytics loopNeeds live PostHog pageview capture after config/deploy.
Blocked
Browser verificationNeeds VQS config: No missing items reported.
Blocked
Checkout pricesNeeds STRIPE_SECRET_KEY with sk_test_/sk_live_ shape plus monthly and annual Stripe price IDs for: No missing items reported.
Blocked
Social proofNeeds No missing items reported. before publish. Metricool status: unknown; brand/mapping satisfied: no; required brand: AIRCITE; provider requirements: No missing items reported.; token-visible brands: No missing items reported.; approved mapping: No approved LUCA-channel mapping reported.; hold reasons: No hold reasons reported.. Scheduled: 0, held: 0, NOLAN pending: 0, CMP01 missing: 0, published 7d: 0.
Blocked
SAFE

Evidence boundary

AIRCITE launch proof stays public enough for operators to verify status and private enough to keep credentials, tenants, and customer records out of the browser.

Secret valuesNever returned by health or readiness views
Blocked
Tenant recordsStay behind Supabase Auth and product membership
Gated
Public proofDomain, config, VQS, analytics, and checkout readiness booleans
Visible
Gate checklist

What must clear

DOMAIN

Domain and deployment proof

Customer-live sign-off requires the expected AIRCITE domain on the current production deployment SHA.

ENV

Runtime configuration

Required public and server environment keys must be present; health responses expose booleans only.

VQS

Browser verification

The VQS browser-render endpoint and browser token are checked by presence only, never by returning secret values.

PAY

Checkout readiness

Stripe secret shape and Supabase price IDs must be configured before self-serve checkout can open.