screen · composed of the kit
How it works
From repositoryto every surface.
Majordomus discovers what a repository declares, builds one typed index and capability registry from it, and projects every interface from that: an HTTP API described by OpenAPI, MCP, the Cockpit and this site, and a command line checked against the registry. One model, many projections.
“Majordomus should discover and model a fact once, then derive every relevant interface from that canonical representation.”
1
Discover
Read what the repository declares
prismatic-majordomus/
- .git/branch, head, history
- .ai/policy, rules, prompts, workflows
- apps/the Rust executable
- docs/manuals, claims, generated
- share/kinds.yaml, schemas, design
- test/527 test objects
- justfilethe recipes a person runs
2
Build
One typed index, one registry
Object index
state ok · 34 kinds
- kinds · sourcesdiscovery, declared
- typed objectscanonical identity
- capabilitiesone descriptor each
- one executorContext::execute
- derived stateproof, evidence, plan
- rule
- adr
- feature
- test
- use-case
- claim
3
Derive
Every interface, projected
- CLI234 commands
- HTTP API/api/v1/
-
OpenAPI · Swagger/swagger
- MCPmajordomus mcp
- Cockpit/cockpit
- DocumentationGitHub Pages
- Generateddocs/generated/
4
Present
A small preview of each surface
$ majordomus context
## GIT repository <repo> branch main head <sha> working_tree dirty task_record exact (recorded head <head>)
- Rules187
- ADRs117
GET
DocumentationRepository and index state
/api/v1/repository
5
Use
What one model buys
- Consistentevery surface reads one registry
- Deterministicthe same input, the same bytes
- Discoveredfound through declarations, not hand-kept lists
- Regeneratedderived files are never edited
- Checkedgenerate --check refuses drift
- People and agentsCLI, API, MCP, pages, docs
- Extensiblea declared capability reaches MCP, HTTP and OpenAPI
Real impact
Measured, or counted.
The token figures measured so far are the context compiler's; the one shown is how much relevant context it leaves out of the budget. Whether a whole session uses fewer tokens is not yet measured, and the token economics page says so.
97.9%
of the relevant context left out of the budget, median of 315 seedseconomics.json · context_reduction_ratio · not total-token savings
0 of 30
valid matched pairs for a total-token claimeconomics.json · verdict: not publishable
197
HTTP operations, each described once by OpenAPIopenapi.json · counts
234
commands in the CLI tree, checked against the same registrycli.json · counts