ToolsObserve planeserves the suite

Console

The control room

StatusBuildRunning
FIG · One surface watches the whole estate, and changes nothing.

Where it stands. Runs today, in daily use. It sits at the Build stage of the ruler.

01What it does
01
Reads the suite as one view
Every Tool’s progress is authored into Console, the single source of truth for how far each has gone, and its live performance is read from the telemetry shape that Tool emits. The two sit on one surface.
02
Watches, never steers
Console changes nothing it looks at. A runtime question it surfaces belongs to the verify plane; a drift it shows belongs to the propose plane. It is the suite’s eyes, not its hands.
03
Honest when a panel is empty
When a Tool has no runtime yet, its Console panel is schema-stubbed and labelled as such, rather than showing a blended score or a number nobody can back.
02Its place on the control plane

Observe is a read-only plane, and Console holds it alone. A runtime question it raises is the verify plane’s Gauge to answer; a drift it shows is the propose plane’s Concord to reconcile. Console never reaches for the write path itself.

03Who it works with

A pairing here means two tools actually exchange something, and the thing they exchange is named.

04Where it does the work