Colour carries meaning, never decoration
| Colour | What it means |
|---|
| Orange | A decision, a command, the critical path. The moment of choice. Used sparingly on purpose - if everything is orange, nothing is. |
| Dark carbon | Authority. Command rails, agent advisory panels, the immutable log. |
| Light canvas | Context - the ground everything is planned on. |
| Green | Passing, healthy, verified. |
| Amber | Needs attention. |
| Red | Blocked, an incident, a failure. |
| Blue | Informational, and specifically an agent proposing something. |
| Grey | Inactive, at rest, done. |
Blue meaning "an agent is proposing" is worth remembering: it is how you tell, at a glance, what was suggested from what was decided.
Every number can explain itself
Health bands, forecasts, runway, readiness, entitlement usage - all computed when you read them, none of them stored, and each able to name what produced it. If a number is on screen, something next to it or behind a click says where it came from.
That is a rule rather than a nicety. A stored score drifts from the thing it was meant to measure, and a score you can edit gets edited to look good.
Refusals appear where you were working
When something is refused, the message and its hint appear at the point of the action - not as a toast that disappears before you can read it. The same three fields an agent receives over MCP are what you see: what happened, and the specific next step.
Light and dark
The interface follows your system theme. The colour roles above hold in both - what changes is the surface they sit on, not what they mean.