Each feature names this domain in its own file; the domain lists none of them. A feature added with this domain is on this page at the next build, and one removed is gone.
-
Declare once
A capability is written in one place, and the command line, the HTTP API, the OpenAPI document, MCP, the Cockpit, the reference and this website are projections of it.
9 of 9 claims guaranteed with a named test · 1 use case
-
Interfaces
Every agent, script and person reads the same repository through the interface it already speaks, and none of the interfaces is maintained by hand.
11 of 11 claims guaranteed with a named test · 3 use cases
-
Observatory
One screen of the UI rotates eight scenes on a display nobody is sitting at, and every mark on it is a value a capability answered; a scene with nothing true to draw says why and is never drawn empty.
1 of 1 claims guaranteed with a named test
-
UI
The shared server's primary surface answers how the delivery stands — health, releases, the roadmap, the work and its pull requests, the mesh, the evidence and the rules — and every value on it names the capability it was read from and every other surface that serves it.
1 of 1 claims guaranteed with a named test
-
Cockpit
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.
1 of 1 claims guaranteed with a named test
-
Install
The installer downloads one archive for your machine, verifies its digest against the release metadata before unpacking anything, and installs atomically; no git, no Rust, no Node, no root.
9 of 9 claims guaranteed with a named test · 5 use cases
-
Why
Every operational moment the tool exists for is one file with the signals that identify it and the mechanisms that answer it, and a reader's own symptoms resolve to a diagnosis by counting, not by inference.
3 of 3 claims guaranteed with a named test · 1 use case