Action needed
Owner Handoff
WarpIntel keeps outside approvals and account-review work separate from buildable app work. This page shows public-safe owner lanes, proof targets, and build-while-blocked work without credentials, private EVE data, protected setup packet contents, raw submissions, or separate-project account details.
Project-owner, provider/account, and feature-gate lanes grouped for review.
Action-needed items waiting on external approval, account access, or review.
Useful build work that can continue while outside blockers wait.
Checklist gates that make this handoff safe to use for launch decisions.
Public surfaces that prove the handoff is reviewable without protected details.
The full public Next Actions queue remains the source of truth.
Top Owner 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.
Project Owner
- Actions
- 4
- Waiting
- 2
- Buildable Now
- No
- Acceptance
- Owner-visible action is named, public-safe, and kept out of provider credentials.
Discord Bot And Role Sync: Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
Provider Or Account Review
- Actions
- 4
- Waiting
- 4
- Buildable Now
- No
- Acceptance
- Provider/account blockers stay visible without exposing account identifiers or setup packet contents.
Transactional Email: Use the protected email setup packet, then wait for Resend approval or choose another approved sender before enabling transactional mail.
Feature Gate Review
- Actions
- 2
- Waiting
- 0
- Buildable Now
- Yes
- Acceptance
- Feature-gated work names the safe public route before any external service is enabled.
Stripe: Create and verify WarpIntel-only support links before enabling the public Stripe flag.
Analytics And Search Verification
Staged for final verification before public activation.
- Area
- Growth
- Next Step
- Use the protected Growth packet when setting up Vercel Analytics, Speed Insights, Search Console, or Bing Webmaster Tools.
Backup And Recovery Packet
Staged for final verification before public activation.
- Area
- Recovery
- Next Step
- Use the protected backup packet during the next release/recovery review and verify an actual Neon restore drill before paid launch.
Sentry Error Monitoring
Staged for final verification before public activation.
- Area
- Monitoring
- Next Step
- 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.
Stripe Support Links
Staged for final verification before public activation.
- Area
- Payments
- Next Step
- Use only the WarpIntel Stripe account to update the business website and create WarpIntel-only links.
EVE SSO
Staged for final configuration, link validation, or smoke testing.
- Area
- EVE Private Data
- Next Step
- Enable public EVE login only after callback, scope map, and live test gates are ready.
Sentry Error Monitoring
Staged for final configuration, link validation, or smoke testing.
- Area
- Monitoring
- 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.
Owner lanes present
Project-owner, provider/account, and feature-gate lanes are separated for review.
Top owner actions present
Each owner-review lane has a public-safe top action.
Waiting work visible
External approval and account-review blockers stay visible without exposing private setup details.
Buildable work visible
Build-team and feature-gate work remains visible while outside approvals wait.
Source Next Actions ready
The source Next Actions manifest is ready and activation handoff is covered.
Public link coverage
Public links reach the owner-handoff page, JSON feed, Next Actions, health, support, and readiness views.
No-secret text boundary
The source action text excludes credentials, private EVE data, protected packet contents, and account details.
Owner handoff page
Public page shows owner-review lanes and buildable work without protected setup packet contents.
Owner handoff JSON
Machine-readable owner handoff feed uses the same no-secret source action data.
Next Actions
Source action board remains the full public action queue.
Launch readiness
Launch blockers remain reviewable as public-safe rows.
Integrations
Provider and account setup lanes remain grouped without exposing credentials.
Health JSON
Public health can verify owner-handoff aggregate counts and no-secret boundaries.
Support
Support remains linked for owner questions without exposing support queue contents.
No-Secret Handoff Rule
Public owner handoff exposes sanitized owner-category lanes, top action summaries, buildable-work counts, activation criteria, proof-target counts, and public links only; it does not expose provider credentials, API keys, passwords, EVE tokens, private EVE data, account data, raw submissions, protected setup packet contents, provider cookies, private logs, or separate-project account details.