> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3iq.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Command Center

The authenticated B3IQ operations surface for nodes, routed work, customers, settlement, incidents, and admin actions.

The command center is the authenticated operational view for B3IQ nodes, routed
work, customers, settlement, and incident posture. It is intentionally described
from contracts and operational behavior here instead of public screenshots,
because the production surface is not a public marketing page.

## What it covers

| Panel | Purpose |
| --- | --- |
| Router playground | Authenticated hosted chat tests against current router candidates and customer policy |
| Nodes | Admin node list, route-readiness summaries, and operator dashboard selection |
| Customers | Customer status, usage, gateway policy, and gateway key creation |
| Hardware orders | Machine orders, payments, and fulfillment status |
| Support | Customer support tickets and staff replies |
| Commands | Command queue state, retry, cancel, and audit export |
| Settlement | Payout batch preview, create, submit, finalize, reset, and inspection |
| Incidents | Pause/resume controls for high-risk or failing traffic classes, plus rate-limit presence and launch-gate checks |

## Safety model

Command center access is role-sensitive. Public traffic controls should not
depend on one broad admin token once production roles exist.

**Command center launch gates**

**Approval storage**

High-risk routes write approval evidence and expose launch-gate posture.
  **Incident controls**

Pause and resume selected traffic classes, customers, nodes, or payout paths
    with required reasons.
  **Production roles**

Add production auth, role separation, multi-actor approval routing, and
    stronger audit trails before public traffic.

## What must stay redacted

Admin and operator surfaces must not leak:

- Raw prompts or model outputs.
- Gateway keys, customer tokens, admin tokens, local keys, support grants, setup tokens, or token hashes.
- Exact private routes, tunnel connector tokens, local URLs, or runtime IDs.
- Raw customer secrets or payment credentials.

## Related

**[Current status](/operations/current-status)**

Understand live pilot evidence and open gates.
  **[Receipts and payouts](/developers/receipts-billing)**

See the settlement and ledger surfaces command center operates on.
  **[Release trust](/operations/release-trust)**

Track installer and update trust posture.