Skip to content

The Cockpit: the registry rendered for a person

At /cockpit the shared server lays out what a capability answered — the registry explorer, every object of the layer, the derived graphs, the directory contracts, the continuity of this checkout, the worktree topology, one health report naming the engine behind every check — and every page is complete HTML before any script runs.

The same server that answers agents renders every capability, object, graph, worktree and health check as pages, with a runner generated from each capability's own schema; nothing on it is a second list.

status
stable
exposed through
area
observability

What it does

Every page asks a capability through the one executor MCP and the HTTP routes use, so the Cockpit cannot answer a question differently from the API. The sidebar's catalogues are the registry's modules, the index's kinds and the graph derivations; a capability's page carries its schemas, its projections, its provenance and a form generated from its input schema that calls its real route. A capability, a kind or a graph added to the backend has a page, a navigation entry and a search entry the first time it exists, with no line of the Cockpit written for it.

The browser layer is an enhancement in the strict sense: a command palette, the runner, a graph drawing and two optional views, under a strict content-security policy with no inline script and no remote origin. With JavaScript off every page still shows everything it knows.

What it does not do

It holds no model, no catalogue and no verdict of its own, and it writes nothing: every capability it can reach is a read, or the one command that changes this process's memory. It is not the published website; that is a static projection of the same registry with no server behind it.

The capabilities behind it

The capability modules of the executable this feature names, each with the capabilities it composes. The command line, the HTTP route, the MCP tool and the reference beside every row are projections of one declaration, not four registrations.

Health health behaviorally verified

Whether what this process serves is healthy, decided by the engines that already decide it: the index's diagnostics, the registry builder, the benchmark projection's coverage and the comparison `generate --check` makes. No check here has an opinion of its own.

apps/majordomus-cli/src/capability/builtin/health.rs

What it answers

Operational moments from the Why catalogue that name one of this feature's mechanisms. Nothing here was assigned: a moment appears because it names a rule, a command, a capability or a claim this feature also names.

The rules that hold it

  • blockingExternal interfaces are projections of one capability definitionproject.interfaces-are-projections