Deploy & CI

Web (marketing + docs)

• Target platform: Vercel
• Prefer preview deployments for review; promote deliberately to production
• Env vars via Vercel project settings; contract in .env.example
• Docs site: not deployed until Phase 1 chrome is reviewed

iOS

• CI via xcodebuild on macOS runners
• Signing / notarization secrets stay in CI vaults — never in git
• TestFlight before App Store when risk is non-trivial

Backend

• Follow the backend repo’s deploy runbook (container / host / migration order)
• Run migrations deliberately; never “hope” schema drift matches prod

Promotion checklist

• Preview / staging validated against the test plan
• Env vars present in the target environment
• Rollback path known (previous deploy / previous build)
• Docs updated if user-facing behavior changed

Related

• Environments
• Observability
• Local setup