Service readiness
Service Readiness Snapshot
WarpIntel keeps production liveness, integration gates, and external setup blockers visible through public-safe summaries while provider credentials, private EVE data, account records, protected packet bodies, raw submissions, and separate-project account details stay excluded.
Tracked platform, EVE, revenue, communications, intelligence, and monitoring lanes.
Feature-flagged, staged, planned, or waiting integration lanes not yet public-active.
Provider, account, or verification lanes still blocked outside the app code.
Open external setup lanes visible through public-safe owner categories.
Fast production liveness is checked separately from the deeper health snapshot.
No-secret visibility, private-data exclusion, protected packet exclusion, and no provider calls.
AdSense
- Owner Category
- Provider or account review
- Critical Lane
- Yes
- Next Step
- Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
Discord
- Owner Category
- Provider or account review
- Critical Lane
- Yes
- Next Step
- Complete Discord app verification, then validate the signed interaction endpoint.
Resend
- Owner Category
- Provider or account review
- Critical Lane
- Yes
- Next Step
- Wait for approved sending provider or fallback before enabling transactional sends.
EVE SSO
- Owner Category
- WarpIntel setup verification
- Critical Lane
- Yes
- Next Step
- Enable public EVE login only after callback, scope map, and live test gates are ready.
Sentry Error Monitoring
- Owner Category
- WarpIntel setup verification
- Critical Lane
- No
- Next Step
- Configure WarpIntel-only DSNs and the capture feature flag only after scrub rules are reviewed and a non-sensitive sample capture is approved.
Stripe
- Owner Category
- Feature-gate review
- Critical Lane
- Yes
- Next Step
- Create and verify WarpIntel-only support links before enabling the public Stripe flag.
Discord Bot And Role Sync
- Owner Category
- Project Owner Review
- 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.
Google AdSense
- Owner Category
- Project Owner Review
- 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.
Transactional Email
- Owner Category
- Provider Or Account Review
- 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.
EVE SSO Callback
- Owner Category
- Project Owner Review
- 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.
Analytics And Search Verification
- Owner Category
- WarpIntel Build Team
- 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.
Backup And Recovery Packet
- Owner Category
- WarpIntel Build Team
- 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.
Production Ping
The fast ping reports alive and delegates deep readiness to the full health snapshot, so production liveness can be checked without database reads, provider calls, OAuth starts, token exchange, or protected-route body exposure.
No-Secret Service Rule
Public service readiness exposes sanitized service counts, public setup lane summaries, public action queues, production ping status, public links, and safety-boundary counts only; it does not expose provider credentials, API keys, passwords, EVE tokens, private EVE data, account records, protected setup packet bodies, raw submissions, provider cookies, private logs, or separate-project account details.