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 |
|---|---|
| Launch posture | Billing requirement, rate-limit presence, approval workflow state, incident controls, and launch checks |
| 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, credits, gateway policy, usage, and gateway key creation |
| 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 |
Safety Model
Command center access is role-sensitive. Public traffic controls should not depend on one broad admin token once production roles exist.
High-risk routes write approval evidence and expose launch-gate posture.
Pause and resume selected traffic classes, customers, nodes, or payout paths with required reasons.
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.