Product / Command· target design · sandbox
The cockpit is a control room, not a chart wall.
Eighteen operational modules, each with real reads and writes, loading, empty and error states, authorization behavior, and reproducible browser tests.
01 / MODULES
What an operator actually touches.
A module is launch-ready only when its backend operations, states, permissions, and tests exist. Decorative charts do not count.
| Module group | Modules |
|---|---|
| Portfolio | Overview · Advertisers · Campaigns |
| Planning | Media Planning · Audiences · Intelligence and Forecasts |
| Execution | OpenRTB Edge · Inventory and Deals · Creatives and Experiments |
| Agent operations | Agent Desk · Tasks and Approvals |
| Money | Spend and Treasury · Billing · Attribution and Measurement |
| Platform | Integrations · API/MCP Developer · Security and Governance |
| Evidence | System Health · Audit and Support |
02 / STATE
Every object shows where it really is.
Money and bid prices use tabular numerals. Timestamps are UTC with a local-zone toggle. States are explicit, and a failed deploy never reads as live.
03 / MONEY
Spend is a ledger, not a gauge.
Treasury views separate available, reserved, settled, and released amounts. A reservation is atomic; a settlement is reconciled.
The cockpit cannot bypass policy. A button and an API call both produce a command envelope and call the same service.
Pending approvals are durable work orders, not toast notifications. Approval binds a named principal to a preview hash.
Approval path
- Preview
- Exact diff and versions
- Decision
- Named approver + hash
- Apply
- Recheck, then execute
- Receipt
- Effects + rollback ref
Test it in the sandbox.
Every surface is exercised against fixtures before a production credential is involved.