The product, by domain
The few things Majordomus controls for AI-assisted work, each with the failure it answers and the features filed under it. Every member, interface and count is derived from the features that name the domain.
-
1 · 4 features
Context
Every worker starts from what the repository already knows: the context that applies to its path, the handover the last session left, and the decisions already made.answers
Agents forget. What one session learned dies with its conversation, and the next one starts over.- claims guaranteed with a named test
- 29 of 32
- executable use cases
- 17
- rules it rests on
- 19
-
2 · 6 features
Coordination
Every worker declares the paths it will touch, sees who else is working and where, and hears about a collision before it is committed.answers
Agents collide. Parallel workers edit the same paths, or build the same thing twice, without knowing about each other.- claims guaranteed with a named test
- 40 of 41
- executable use cases
- 6
- rules it rests on
- 13
-
3 · 3 features
Governance
The rules are written once, in the repository, projected into every tool's instructions, and a blocking rule stops the command instead of advising it.answers
Rules drift. Each tool keeps its own instruction file, and a rule nobody wired into enforcement is only a suggestion.- claims guaranteed with a named test
- 25 of 29
- executable use cases
- 8
- rules it rests on
- 17
-
4 · 5 features
Evidence
A claim names the test that settles it, a recorded run is judged against the commit it ran at, and a claim with no recorded run says so.answers
Claims outrun proof. The documentation says one thing, the runtime does another, and nobody can show which is true.- claims guaranteed with a named test
- 30 of 34
- executable use cases
- 4
- rules it rests on
- 13
-
5 · 3 features
Completion
Done is a contract the repository evaluates line by line. Work is not accepted while any line fails, and a refusal stays on the record.answers
Done is cheap. A worker can report success before the repository's own checks hold.- claims guaranteed with a named test
- 16 of 16
- executable use cases
- 8
- rules it rests on
- 12
-
6 · 7 features
Surfaces
One declaration in the repository becomes the command line, the HTTP API, MCP, the UI, the Cockpit, the documentation and this site, and a projection that disagrees with it fails the build.answers
Interfaces disagree. The command line, the API, the docs and the website each keep a copy, and the copies drift.- claims guaranteed with a named test
- 35 of 35
- executable use cases
- 10
- rules it rests on
- 15
How a feature lands in a domain
A domain is one file under .ai/repo/features/domains/ with its promise and the failure it answers. A feature names exactly one domain in its own file. Everything above is derived from those two facts at build time: the members, the interfaces, the guarantees and the counts. A feature that names no domain, or one that does not exist, fails validation before a page is built.
Every feature → Every feature against every interface → The failure modes, by area of work → How this page is derived →