Every limitation below is a fact about the current implementation, not a disclaimer. Several are the reason a claim is marked advisory or planned in the guarantees matrix.
- Majordomus is invoked by a person, a git hook, a worker following its instructions, or the worker's own session hooks. Those hooks run only at session and prompt boundaries, to record the session and hand it its briefing, and always let the worker continue: nothing inspects or refuses a tool call. Only Claude Code's hooks are wired; Codex and Gemini have hooks this tool has no adapter for yet.
- It measures tokens only in matched runs with and without it, and states a saving only
once its publication rule is met. It measures no money: cost is the harness's own
projection, not a bill.
docs/ECONOMICS.mdsays what else is not measured. - Scope overlap between worktrees is reported, never blocked. Where a repository opts into the mesh, an exclusive claim refuses an overlapping one on every linked machine; that is a lease, not a lock, and during a network split both sides can claim.
- Where a profile requires a regression test,
finishchecks only whether a test-shaped path was touched (atestorspecdirectory, a_test.or.spec.file name), not what the test proves. - The YAML subset is deliberately small: maps, lists, lists of maps, inline lists, quotes, comments. Tabs and odd indentation are refused; the Rust reader also refuses anchors, aliases and block scalars, which the shell reader takes as text. A flow map is not parsed as a map.