Mandately documentation
Mandately keeps your team's rules for who may decide what, per kind of work, as files in your repository. We call these rules the mandate. Your agents work inside it, and every decision is recorded on one ledger.
Start here
Read the install guide. It covers what the machine needs, the access to give it, the 6 questions of the setup and how to keep the watch running.
The commands
| command | what it does |
|---|---|
mand init | asks 6 questions, then opens a pull request with your rules |
mand baseline | measures your team's history from git and the board, once |
mand watch | records each new event with what your rules say about it, and changes nothing |
mand report | shows the week beside your baseline |
mand runner check | checks that each place your agents run holds only what your zones allow |
Each one takes --help for its options.
Your rules
Your rules live in .mandately/ in your repository, and change by pull request. How rules work explains them, with a page for each file:
| file | what it holds |
|---|---|
people.yml | who is accountable, who may say release, go and ship, and which accounts are agents |
classes.yml | the impact classes, from A (irreversible or external) to E (reading and reporting), and whose word each needs |
sensitive.yml | paths that always need the owner's go, whatever the class |
lifecycle.yml | the states work moves through, which board status means which, and how a fix is marked |
connections.yml | the board and the repositories Mandately reads, with no credentials |
prices.yml | optional: what each model's tokens cost, so an agent's run has a cost |
zones.yml | optional: the places your agents run, and what each may hold |
The source
The source is published with the first release. Mandately is open core: the core is source available under the Business Source License 1.1, and the connections are open source under Apache-2.0.