Carry operations
Carry systems that are actually connected
The current production stack exposes carry data through Kingdom state, Kingdom Nexus and the private HQ API bridge. This page no longer advertises slash commands, payout flows or sample sessions that are not in the deployed command registry.
Source of truth
One live carry state
Nexus and the public HQ consume Kingdom Core state rather than maintaining separate sample queues or browser-only records.
Command Centre
Production data loads after Discord sign-in
—
—
—
—
Implemented
Connected carry surfaces
Live queue state
Kingdom state exposes active carry records and queue demand to Nexus and the public HQ bridge.
Learn moreActive sessions
The native Nexus live payload includes current carry/session information and can stream updates over Server-Sent Events.
Learn moreWebsite carry creation
The HQ bridge contains a token-protected carry-creation endpoint used by the authenticated public website request flow.
Personal carry history
The HQ bridge exposes authenticated member carry-history reads rather than showing fabricated example sessions.
Operational totals
The HQ overview is calculated from current Kingdom state, including waiting, active, running and completed-player counts.
Live operational view
Kingdom Nexus is the authoritative staff-facing web surface for carry state; the separate mock dashboard has been retired.
Learn moreOpen 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.