External setup
External Setup
WarpIntel keeps provider and account blockers visible without exposing protected setup packets, provider credentials, private EVE data, or separate-project account details.
Provider, account, feature-gate, and setup lanes still waiting or staged.
Blocked lanes that need provider, account, or owner review before activation.
Admin-only setup packets counted for handoff without public packet bodies.
Work the build team can continue while outside approvals are unresolved.
Public pages and feeds proving the setup board stays reviewable and no-secret.
Required safeguards before this feed is trusted for launch decisions.
Top Setup Action
Discord Bot And Role Sync: Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
Discord Bot And Role Sync
- Area
- Comms
- Owner Category
- Project Owner Review
- Blocker
- The app-side command manifest is staged, but Discord human verification is still blocking the bot application, public key, and token setup.
- Next Action
- Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
- Allowed Now
- The build team can keep app-side work moving, but the account or verification step needs owner review.
- Protected Packet
- Counted, admin-only
Google AdSense
- Area
- Ads
- Owner Category
- Project Owner Review
- Blocker
- Google account verification is still required before AdSense site review can finish.
- Next Action
- Complete Google verification on Zeus, then finish AdSense submission and store the publisher/client ID.
- Allowed Now
- The build team can keep app-side work moving, but the account or verification step needs owner review.
- Protected Packet
- Counted, admin-only
Transactional Email
- Area
- Owner Category
- Provider Or Account Review
- Blocker
- The email provider account is still under provider review, so app email sending remains off.
- Next Action
- Use the protected email setup packet, then wait for Resend approval or choose another approved sender before enabling transactional mail.
- Allowed Now
- The build team can keep the lane staged while provider approval clears or an approved replacement is chosen.
- Protected Packet
- Counted, admin-only
EVE SSO Callback
- Area
- Auth
- Owner Category
- Project Owner Review
- Blocker
- Partially configured: Client credentials, publicData first-login scope, and the exact WarpIntel callback are staged; public sign-in remains hidden until the feature flag and live sign-in test are approved.
- Next Action
- Keep public sign-in feature-flagged off until the controlled live sign-in test is approved and recorded.
- Allowed Now
- The build team can keep app-side work moving, but the account or verification step needs owner review.
- Protected Packet
- Counted, admin-only
Analytics And Search Verification
- Area
- Growth
- Owner Category
- WarpIntel Build Team
- Blocker
- Partially configured: Vercel telemetry is available; search verification tokens can be added after provider setup.
- Next Action
- Use the protected Growth packet when setting up Vercel Analytics, Speed Insights, Search Console, or Bing Webmaster Tools.
- Allowed Now
- The build team can keep working this lane inside the dedicated WarpIntel accounts and infrastructure.
- Protected Packet
- Counted, admin-only
Backup And Recovery Packet
- Area
- Recovery
- Owner Category
- WarpIntel Build Team
- Blocker
- Partially configured: Protected backup-readiness packet is staged, but a real Neon restore drill is not marked complete yet.
- Next Action
- Use the protected backup packet during the next release/recovery review and verify an actual Neon restore drill before paid launch.
- Allowed Now
- The build team can keep working this lane inside the dedicated WarpIntel accounts and infrastructure.
- Protected Packet
- Counted, admin-only
Sentry Error Monitoring
- Area
- Monitoring
- Owner Category
- WarpIntel Build Team
- Blocker
- Partially configured: Sentry SDK instrumentation is installed with scrub rules, but capture remains off until WarpIntel DSNs and the explicit feature flag are approved.
- Next Action
- Add WarpIntel-only Sentry DSN env vars, keep sourcemap upload disabled until a Sentry auth token exists, and verify a non-sensitive sample capture after the project owner approves the provider setup.
- Allowed Now
- The build team can keep working this lane inside the dedicated WarpIntel accounts and infrastructure.
- Protected Packet
- Counted, admin-only
Stripe Support Links
- Area
- Payments
- Owner Category
- WarpIntel Build Team
- Blocker
- Partially configured: A separate WarpIntel Stripe account exists; public voluntary support or donation links still need a WarpIntel-scoped live dashboard check.
- Next Action
- Use only the WarpIntel Stripe account to update the business website and create WarpIntel-only links.
- Allowed Now
- The build team can keep working this lane inside the dedicated WarpIntel accounts and infrastructure.
- Protected Packet
- Counted, admin-only
Production AI Key
- Area
- AI
- Owner Category
- Project Owner Review
- Blocker
- Feature is currently off: The app is using deterministic analysis until the project owner chooses which approved OpenAI account should fund WarpIntel production usage.
- Next Action
- Add the approved WarpIntel/Olympus OpenAI key and enable NEXT_PUBLIC_ENABLE_OPENAI only when production AI spend is approved.
- Allowed Now
- The build team can keep app-side work moving, but the account or verification step needs owner review.
- Protected Packet
- Counted, admin-only
Open external setup lanes visible
External setup blockers are visible as sanitized public rows.
Waiting lanes separated
Provider or owner blockers are separated from staged work.
Provider review lane named
Provider/account blockers are represented by public categories.
Protected packets counted
Protected setup packets are counted and summarized without public packet URLs or bodies.
Build-while-blocked lane visible
Build-team work remains visible while outside approvals wait.
Public proof links
The public setup board links to safe readiness pages instead of protected admin packets.
No-secret public setup surface
Provider credentials, private EVE data, and separate-project account details are excluded.
External setup page
Public page renders open setup lanes without protected packet bodies.
External setup JSON
Machine-readable feed excludes secret-like values and protected setup packet contents.
Launch readiness
Launch lane status remains the source for external setup blockers.
Integrations
Provider-service readiness stays linked without exposing provider accounts.
Next actions
Build-while-blocked work remains available while outside approvals wait.
Owner handoff
Owner-visible actions stay grouped separately from provider credentials.
Health JSON
Aggregate health can verify external setup counts and no-secret boundaries.
No-Secret Setup Rule
Public external setup readiness exposes sanitized blocker labels, public owner categories, protected setup-packet coverage counts, public proof links, and build-while-blocked summaries only; it does not expose protected setup packet bodies, provider credentials, API keys, passwords, EVE tokens, private EVE data, account data, raw submissions, provider cookies, private logs, or separate-project account details.