Public Capability Safety
Capability Readiness
WarpIntel capability readiness checks whether the public toolset, browser-local workflows, protected review queues, EVE SSO consent gates, and external provider gates are mapped with clear no-secret boundaries. First login stays scoped to publicData; deeper features use feature-specific previews before private EVE permissions or provider services are enabled.
No-secret capability coverage is ready.
Live, local, protected, EVE-gated, and provider-gated capability paths.
Public-facing routes represented in the capability matrix.
EVE SSO feature previews staged before private scope requests.
Live Public Tools
Usable without EVE sign-in, provider approval, or private character data.
Browser-Local Workflows
Working state stays in the visitor browser unless they export it or later opt into account sync.
Protected Review Queues
Public intake and advisory boards stay human-reviewed before protected reviewers take action.
EVE SSO-Gated Modules
Private EVE modules are staged with consent previews and wait for feature-specific user approval.
External Provider Gates
Payments, ads, email, Discord, AI, monitoring, and other providers remain feature-flagged until ready.
public capabilities
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
browser-local workflows
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
protected review queues
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
EVE SSO consent gates
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
external-provider gates
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
secret exclusion
Public capability readiness exposes aggregate capability counts, route-link counts, consent-preview counts, provider-gate counts, link counts, and safety-boundary counts only; it does not expose provider credentials, EVE tokens, private EVE data, account data, raw submissions, private logs, hidden setup packets, internal account names, or separate-project account details.
The public capability matrix lists public routes, browser-local tools, protected review queues, EVE SSO consent timing, and provider-gate labels only. It excludes credentials, tokens, account details, private EVE data, raw submissions, hidden setup packets, and separate-project account details.