The operating platform behind Kingdom Carries
Kingdom Core joins the Discord runtime, authenticated Nexus, live operations, identity, security, backups, analytics and developer surfaces around one Kingdom state.
No made-up guild counts, uptime percentages or setup-time claims are shown here. Current reachability is reported on the status page.
Command Centre
Production data loads after Discord sign-in
—
—
—
—
Live operations
System intelligence
Current source
Capabilities that exist in Kingdom Core now
The sections below are based on the production Core/Nexus source rather than future roadmap cards or simulated dashboard values.
Kingdom Core runtime
The Discord runtime currently contains the gateway, carry operations, applications, moderation/security and maintenance automation.
- Discord gateway
- Carry operations
- Applications and moderation
Kingdom Nexus
The production web control plane uses Discord sessions and exposes live state, operator controls and a documented API.
- Discord identity
- Live operations
- Permission-checked controls
Kingdom Sentinel
Security posture and incident tooling built from live guild permissions and Kingdom state.
- Risk snapshots
- Dangerous-permission visibility
- Incident lifecycle
Kingdom Vault
State backup and disaster recovery with retention, SHA-256 verification and explicit restore actions.
- On-demand snapshots
- Verification
- Restore workflow
Kingdom Intelligence
Operational analytics generated from Kingdom state, including queue, carry, case and resource telemetry.
- Operational snapshots
- Trend history
- Resource telemetry
Market Intelligence
The deployed /value command can value items or compare a requested gold amount against the current KMI fair-value model.
- Item autocomplete
- POT-aware estimates
- Fair-trade checks
Getting started
Use the command set that is actually deployed
The current top-level slash commands are /setup3, /uipgrade, /mod and /value. Setup should be previewed before it is applied.
- 1
Add Kingdom Core to Discord
Use the current Discord application install flow and review the permissions Discord presents before authorizing it.
- 2
Preview, then apply /setup3
Run /setup3 preview:true first. If the proposed organization is correct, run /setup3 to apply the curated layout.
- 3
Open the production Nexus
Use Discord sign-in on Kingdom Nexus for the authenticated web control plane and live system state.
Production architecture
One authoritative Nexus
The separate mock dashboard has been retired. Web operations now resolve to the Nexus served by Kingdom Core, using its own Discord session, API, live stream and permission checks.
Discord runtime
The bot receives Discord events and runs the deployed setup, moderation, presentation and market-intelligence commands.
Nexus control plane
The web app reads live Kingdom state and protects privileged reads and writes with Discord session and operator checks.
Public health
The website status page calls the production Nexus /health endpoint and reports unavailable when that check fails.
Open the current Kingdom Core stack
Add the Discord application, preview the current /setup3 layout before applying it, and use the production Nexus for authenticated web operations.