Discord
Discord Readiness
WarpIntel can stage Discord command and interaction coverage while bot setup, guild rollout, and command registration stay gated behind protected review. This page exposes aggregate readiness only, without bot tokens, app identifiers, guild identifiers, public keys, install URLs, or Discord API URLs.
Guild command registration remains disabled until the feature flag and protected setup gates are ready.
Slash-command categories are staged for help, status, intel, fit, and loss workflows.
Command manifest and interaction status routes are monitored without exposing provider identifiers.
Protected dry runs do not call Discord, register commands, or mutate provider state.
Discord app, endpoint, guild rollout, bot env, role sync, and tracker review stay owner-gated.
Wrong app, signature failure, and unexpected provider mutation each have a safe stop path.
WarpIntel-only Discord app boundary
Protected setup guidance keeps the Discord application, bot, guild rollout, and role-sync lane inside a separate WarpIntel project boundary.
Signed interaction endpoint
Public command handling stays inactive until Discord endpoint validation can verify signed requests through the protected setup gate.
Public key and app identity gate
Activation requires reviewed Discord app identity values, while public readiness exposes only aggregate booleans and counts.
Bot token and first-guild gate
Command registration remains blocked until the bot credential and first test server are configured through protected admin setup.
Role-sync feature gate
Discord role sync remains feature-gated and cannot mutate roles until bot setup, EVE consent mapping, and human admin review are ready.
Guild slash-command registration review
The first rollout uses protected guild command registration before any broader Discord command deployment.
Protected dry run without Discord mutation
Protected dry runs preview command registration and role-sync boundaries without calling Discord or changing provider state.
Public no-secret smoke coverage
Production smoke covers Discord readiness JSON, public health counters, protected admin denial, and secret-exclusion boundaries.
Discord App Boundary Review
Confirm the Discord application and bot are WarpIntel-only before endpoint validation or command rollout.
Interaction Endpoint Validation
Validate signed interactions through the WarpIntel endpoint without publishing public keys or provider identifiers.
Guild Command Rollout Review
Review the first guild command payload and keep broader command rollout blocked until the test server is accepted.
Bot Token Env Review
Confirm bot credentials stay only in private runtime configuration and are never echoed in public readiness.
Role Sync Consent Review
Keep role sync disabled until EVE consent mapping and human role-mapping review are accepted.
Tracker Record
Record only secret-free command-state, endpoint-state, role-sync gate, commit, deployment, and rollback outcomes.
Wrong Discord App Or Guild
Wrong app or guild scope stops Discord activation before endpoint validation or command rollout is accepted.
Endpoint Signature Validation Failure
Signature validation failure keeps commands gated until the interaction endpoint proves safe again.
Unexpected Command Registration Or Role Mutation
Unexpected provider mutation rolls Discord back to dry-run-only status before another rollout attempt.
status
Prepared for Discord slash-command use after protected setup, feature-flag review, and smoke testing.
help
Prepared for Discord slash-command use after protected setup, feature-flag review, and smoke testing.
intel
Prepared for Discord slash-command use after protected setup, feature-flag review, and smoke testing.
fit
Prepared for Discord slash-command use after protected setup, feature-flag review, and smoke testing.
loss
Prepared for Discord slash-command use after protected setup, feature-flag review, and smoke testing.
Bot Tokens
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Client Ids
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Guild Ids
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Public Keys
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Install Urls
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Discord Api Urls
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Discord Role Assignments
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Private Eve Data
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Raw Pasted Inputs
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Protected Setup Details
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
No-Secret Discord Rule
Public Discord readiness exposes aggregate command counts, public route names, command category labels, activation criteria, owner-handoff counts, rollback decision counts, activation-rehearsal counts, readiness booleans, protected-check booleans, and no-provider-call dry-run status only; it does not expose bot tokens, app client identifiers, guild identifiers, public keys, install URLs, provider API URLs, role assignment data, cookies, authorization headers, EVE tokens, private account data, or raw pasted analyzer inputs.