Roadmap
WarpIntel Build Plan
The roadmap separates what is live today from protected operations and gated private-data integrations. Public tools ship first, while EVE private scopes, Discord, email, payments, ads, AI, and observability stay behind review gates until they are ready.
Public MVP lanes available without private EVE sign-in.
Private EVE and external provider lanes held behind feature flags.
Public, local, and manual-review routes already listed in the tool directory.
Public MVP
Public tools, local planning surfaces, and manual review workflows that can operate before private EVE SSO is enabled.
- Lanes: 4
- First EVE sign-in scope: publicData
Analyzer Workbench
Intel, fitting, loss, appraisal, market, alliance, fleet, SRP, recruiting, hauling, mining, and industry analysis lanes.
- Status: live
- Now: Visitors can use public advisory tools without signing in.
- Next: Optional AI assistance remains behind feature flags until provider setup and cost controls are ready.
- Boundary: User-entered text is processed as public advisory input and is not saved to an account report.
Public EVE Data Tools
Profiles, system risk, routes, market, industry, PI, sovereignty, and public guides.
- Status: live
- Now: Public ESI, static data, and source-linked reference pages are available now.
- Next: Add richer saved watchlists after account sync is enabled by user choice.
- Boundary: Public EVE data and reviewed static data only; no private wallet, asset, mail, or location reads.
Browser-Local Planning
Fit Lab, skills, reports, watchlists, audits, structure watch, PvE, and wormhole planning.
- Status: live
- Now: Planning state stays in the visitor browser unless manually exported.
- Next: Offer account sync only after EVE sign-in and data-rights controls are ready.
- Boundary: No server-side profile or private EVE pull is required for current local planning workflows.
Manual Review Workflows
Access, recruiting, SRP, buyback, mining, fleet board, and support intake.
- Status: live
- Now: Requests can enter protected queues while review and payout actions stay human-approved.
- Next: Connect reviewer notifications and optional Discord updates after external providers are approved.
- Boundary: Submissions are not shown publicly and do not trigger automatic EVE, Discord, wallet, or role changes.
Trust And Operations
Public trust pages and protected admin exports that make the launch state inspectable without exposing private data.
- Lanes: 2
- First EVE sign-in scope: publicData
Public Trust Pages
Status, releases, roadmap, trust, legal, sources, attribution, security, data rights, ads, privacy, and terms.
- Status: live
- Now: Players, reviewers, and monitors can inspect what is live, gated, sourced, and no-secret.
- Next: Keep release notes and public manifests current with each production slice.
- Boundary: Public pages expose aggregate readiness, policy text, and source labels only.
Protected Ops Exports
Admin-only route smoke, launch blockers, external readiness, ops snapshot, and queue exports.
- Status: protected
- Now: Operators get review packets without making provider credentials or private EVE data public.
- Next: Add signed-in reviewer workflows once the admin account policy is finalized.
- Boundary: Protected exports require admin access; public health shows counts and safe links only.
Private EVE And Integrations
Private EVE scopes, account sync, Discord, transactional email, support revenue, ads, AI, and monitoring integrations remain behind explicit gates.
- Lanes: 2
- First EVE sign-in scope: publicData
EVE SSO Private Modules
Character, corporation, wallet, asset, PI, fleet, and SRP modules that need explicit EVE consent.
- Status: gated
- Now: The first login boundary is staged around publicData before feature-specific private scopes.
- Next: Enable test sign-in only after EVE production callback and approved scopes are confirmed.
- Boundary: Private EVE data is excluded from public pages, analytics, screenshots, logs, and public manifests.
External Provider Lanes
Discord commands, Resend email, Stripe support, AdSense, OpenAI assistance, Sentry, and growth telemetry.
- Status: gated
- Now: Public pages render safe placeholders and dry-run readiness while provider setup finishes.
- Next: Turn on each integration only after credentials, provider review, and feature flags are ready.
- Boundary: Provider credentials, payment profile details, ad scripts, bot tokens, and AI calls stay gated.
The public roadmap lists public pages, protected-route labels, readiness status, and high-level milestones only. It never includes credentials, token values, private EVE data, account exports, raw queue notes, raw logs, raw IP addresses, or private provider setup details.