Project next actions
Next Actions
WarpIntel separates provider/account blockers from work that can still move forward. This public view shows sanitized action categories, counts, and links only, without provider credentials, private EVE data, protected setup packet contents, or separate-project account details.
Combined launch and integration actions that remain gated or staged.
Provider, account, or owner-review lanes that block public activation.
Useful work that can continue while external review lanes are unresolved.
EVE, revenue, and communications lanes tied to launch readiness.
Required public action-board safeguards are tracked before launch decisions depend on this feed.
Project-owner, provider/account, build-team, and feature-gate action lanes are grouped for review.
Public surfaces that prove the owner handoff, blocked lanes, and buildable work are reviewable.
Top Public 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.
WarpIntel Build Team
- Actions
- 6
- Waiting
- 0
- Buildable Now
- Yes
- Acceptance
- Build-team work remains available while outside approvals wait.
Analytics And Search Verification: Use the protected Growth packet when setting up Vercel Analytics, Speed Insights, Search Console, or Bing Webmaster Tools.
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.
Merged launch and integration queue
The board combines launch blockers and integration blockers into one sanitized priority queue.
Waiting and staged work separated
Provider/account blockers are separated from staged work that can still move forward.
Build-while-blocked lanes
Useful build-team and feature-gate work remains visible while outside approvals are unresolved.
Public owner categories
Actions are grouped by public owner category instead of private account names or internal identities.
Activation handoff groups
Project-owner, provider/account, build-team, and feature-gate lanes each have a public-safe top action.
Critical external lanes prioritized
EVE, revenue, and communications blockers remain visible as critical external follow-up lanes.
Public link coverage
The board links to public readiness pages and manifests while protected setup packets stay private.
Protected setup packets linked, not expanded
Protected setup packet contents stay admin-only; the public board links to readiness surfaces only.
No-secret public action surface
Secret-like values, private EVE data, provider credentials, and separate-project account details are excluded.
Next Actions page
Public page renders the merged action queue, owner categories, activation handoff, and buildable lanes.
Next Actions JSON
Machine-readable feed excludes secret-like values, private EVE data, and protected setup packet contents.
Launch readiness
Launch blockers remain visible as public-safe action rows.
Integration readiness
Provider and account setup lanes remain grouped without exposing account credentials.
Health JSON
Public health can verify aggregate next-action coverage, link counts, and no-secret boundaries.
Status page
Status remains the public operator summary for readiness and production checks.
Roadmap
Roadmap context stays available for launch and post-launch sequencing.
Permissions
Permission review remains linked for EVE SSO and feature-specific consent decisions.
Support
Support contact remains linked for public review without exposing support queue contents.
Build while blocked
Build-team and feature-gate lanes stay visible while outside approvals wait.
Activation handoff
Owner, provider/account, build-team, and feature-gate handoff groups have ready public safeguards.
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.
Discord Bot And Role Sync
- Owner Category
- Project owner review
- Area
- Comms
- Next Step
- Complete Discord human verification on Zeus, then add the app public key, client ID, bot token, and guild ID.
- Impact
- Waiting on provider review, account verification, or owner action.
Google AdSense
- Owner Category
- Project owner review
- Area
- Ads
- Next Step
- Complete Google verification on Zeus, then finish AdSense submission and store the publisher/client ID.
- Impact
- Waiting on provider review, account verification, or owner action.
Transactional Email
- Owner Category
- Provider review
- Area
- Next Step
- Use the protected email setup packet, then wait for Resend approval or choose another approved sender before enabling transactional mail.
- Impact
- Waiting on provider review, account verification, or owner action.
AdSense
- Owner Category
- Provider or account review
- Area
- Revenue And Growth
- Next Step
- Finish Google verification and keep ad slots hidden until publisher and slot IDs are approved.
- Impact
- Cannot activate public provider behavior until verification or approval clears.
Discord
- Owner Category
- Provider or account review
- Area
- Comms
- Next Step
- Complete Discord app verification, then validate the signed interaction endpoint.
- Impact
- Cannot activate public provider behavior until verification or approval clears.
Resend
- Owner Category
- Provider or account review
- Area
- Comms
- Next Step
- Wait for approved sending provider or fallback before enabling transactional sends.
- Impact
- Cannot activate public provider behavior until verification or approval clears.
Analytics And Search Verification
- Owner Category
- WarpIntel build team
- Area
- Growth
- Next Step
- Use the protected Growth packet when setting up Vercel Analytics, Speed Insights, Search Console, or Bing Webmaster Tools.
- Impact
- Staged for final verification before public activation.
Backup And Recovery Packet
- Owner Category
- WarpIntel build team
- 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.
- Impact
- Staged for final verification before public activation.
EVE SSO Callback
- Owner Category
- Project owner review
- Area
- Auth
- Next Step
- Keep public sign-in feature-flagged off until the controlled live sign-in test is approved and recorded.
- Impact
- Staged for final verification before public activation.
Sentry Error Monitoring
- Owner Category
- WarpIntel build team
- 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.
- Impact
- Staged for final verification before public activation.
Stripe Support Links
- Owner Category
- WarpIntel build team
- Area
- Payments
- Next Step
- Use only the WarpIntel Stripe account to update the business website and create WarpIntel-only links.
- Impact
- Staged for final verification before public activation.
EVE SSO
- Owner Category
- WarpIntel setup verification
- Area
- EVE Private Data
- Next Step
- Enable public EVE login only after callback, scope map, and live test gates are ready.
- Impact
- Staged for final configuration, link validation, or smoke testing.
Sentry Error Monitoring
- Owner Category
- WarpIntel setup verification
- 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.
- Impact
- Staged for final configuration, link validation, or smoke testing.
Production AI Key
- Owner Category
- Project owner review
- Area
- AI
- Next Step
- Add the approved WarpIntel/Olympus OpenAI key and enable NEXT_PUBLIC_ENABLE_OPENAI only when production AI spend is approved.
- Impact
- Held behind an explicit feature flag.
Stripe
- Owner Category
- Feature-gate review
- Area
- Revenue And Growth
- Next Step
- Create and verify WarpIntel-only support links before enabling the public Stripe flag.
- Impact
- Held behind an explicit public feature flag.
OpenAI
- Owner Category
- Feature-gate review
- Area
- Intelligence
- Next Step
- Keep deterministic tools live until production AI spend and key ownership are approved.
- Impact
- Held behind an explicit public feature flag.
No-Secret Action Rule
Public next actions expose sanitized launch and integration action labels, statuses, owner categories, links, next-step summaries, build-while-blocked counts, proof-target counts, and activation-criteria counts only; they do 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.