Getting started and adoption
Bringing Majordomus into a repository, new or old, without losing what people already wrote.
Bringing Majordomus into a repository, new or old, without losing what people already wrote.
- use cases
- 5
- guaranteed
- 5
-
guaranteed basic
Adopt a repository that already has its own rules
Install the supervisory layer into a repository with a hand-written CLAUDE.md, without the tool taking ownership of a file somebody else wrote.
init · update · doctor -
guaranteed basic
Install the tool in one command, on a machine with no toolchain
Paste one line, get a verified binary for this machine, and run majordomus init — no git, no Rust, no Node, no Python, no root, and no way to install an archive whose digest does not match.
version · init · doctor -
guaranteed basic
Check the version before trusting a diagnosis
Print the version every other surface derives from, and see the argument it refuses.
version -
guaranteed basic
Move a repository from the pre-.ai layout to the layer
See what a migration would move, move it with a backup, and prove the result is a layer the tool reads.
migrate · doctor -
guaranteed basic
Use the tool as your own in a shared repository, and propose it to the team when it has made its case
One flag installs the same layer as yours alone: no tracked file changes, nothing is added to .gitignore, git status reads the same — the command checks it — and one more command hands the layer to the team.
init · update · doctor