Engineering · Console
The fleet console.
Operators used to log into thirteen separate systems to see what the fleet was doing. The console folds them into one shell with four lenses — and every lens is derived from the registry, never hand-maintained.
The shape
One shell, four lenses.
Shell
The persona-aware frame. Which lenses you see is derived from your role on the platform's single identity layer — nothing is hardcoded per user.
Infrastructure lens
Hosts, services, deploys, logs, alerts — the thirteen systems as one pane, read through a broker over the fleet's metrics, logs, and uptime surfaces.
Product lens
The capability catalog and per-product health, read from the same capability graph this site's topology page quotes.
Design lens
The extracted shared design source — one token set instead of a fork per surface.
Status
Where the console stands.
The unified-console fork was ratified 2026-07-21, amended 2026-08-09, and its tracks are sequenced behind the ratification gate. The four-lens interface is shipping live; the infra and product lenses are the tracks in flight.
The console is an internal surface. Its build program is public: the plan.