Key features
Multiple interfaces.One consistent reality.
The same repository state on every surface: the command line, the HTTP API, OpenAPI and Swagger UI, the Cockpit, MCP and this documentation. A surface may render a fact differently; it may not hold a second opinion about it.
“Development semantics live in the canonical runtime; a surface only consumes them”
CLI
The task lifecycle, recorded
started t-<id> profile=implementation scope=lib INFO handover .ai/local/state/handovers/<time>--main--<head>--<hash>.md — prior record, same_worktree_same_branch, exact, <age> ago [reproduce: majordomus handover --resolve] next: majordomus context; checkpoint every 15m; majordomus check before claiming anything
.ai/local/state/checkpoints/<time>--main--<head>--<hash>.md
REST API
Programmable access
/api/v1/repository
Response
{
"repository": RepositoryInfo,
"state": State,
"objects": integer (uint),
"kinds": map of integer (uint),
"diagnostics": array of Diagnostic,
"capabilities": Summary
}cURL
curl -s "http://127.0.0.1:8741/api/v1/repository"
OpenAPI / Swagger
Interactive API documentation
Majordomus API
OpenAPI 3.1.0197 operations; Swagger UI at /swagger.
GET/api/v1/repository
Repository and index state. The repository root, layer sections, git state, discovery mode, kinds present, every diagnostic, and the capability registry counted.
GET/api/v1/rules
Every rule against the proof there is for it. The whole rule corpus joined to the tree and the ledger: per rule, its class, its enforcement mode, the validator and the cases it names, wh…
GET/api/v1/environment
The repository environment. One snapshot of this checkout: project identity, repository identity, version control, declared toolchains, what the layer holds counted per…
GET/api/v1/search
Search objects. Case-insensitive substring search over identities, titles, descriptions and content.
POST/api/v1/plan/transition
Move one issue through the lifecycle. Record that execution of an issue began (`start`), that implementation is complete with evidence outstanding (`verify`), or that it is finis…
MCP Server
Tools for AI agents
Tools
- majordomus_repositoryRepository and index state
- majordomus_rulesEvery rule against the proof there is for it
- majordomus_environmentThe repository environment
- majordomus_searchSearch objects
- majordomus_plan_transitionMove one issue through the lifecycle
Resources
- majordomus://environmentThe repository environment
- majordomus://planThe whole derived plan
- majordomus://changelogThe changelog
- majordomus://repositoryRepository and index state
- majordomus://rulesEvery rule against the proof there is for it
- majordomus://<kind>/<identity>every object of the index
RepositoryReport
The repository root, layer sections, git state, discovery mode, kinds present, every diagnostic, and the capability registry counted.
- adr
- application
- area
- audience
- claim
- command
- context
- critique
- deployment
- derive-offload
- distribution-model
- document
- domain
- feature
- gap
- implementation
- intent
- issue
- knowledge
- mesh-declaration
- milestone
- moment
- policy
- profile
- prompt
- release-record
- rule
- scope
- session
- skill
- taxonomy
- test
- use-case
- workspace
Documentation
Built from the repository
-
majordomus init -
majordomus update -
majordomus doctor
Cockpit
Visual overview, served at /cockpit; pictured here from the generated data
Repository overview
- Rules187
- Decisions117
- Skills8
- Tests527
Decisions per release
oldest first, from the changelog
Changes in 0.29.0
- One declarationeach capability, once, in the executable
- Projectedevery surface reads the same registry
- Discoveredthe layer, from tracked files
- Checked187 rules, each with a derived proof state
- Extensiblea new capability reaches MCP, HTTP and OpenAPI from its declaration