People

people.yml says who is accountable, who else holds each right, and which accounts are agents. Every verdict reads it.

The default

# Who is accountable, and who holds each right. `mand init` fills this from the interview.
owner: [owner]            # the accountable person or people: they hold every right below
roles:
  release: []             # may start work that needs a person's release
  go: []                  # may say go: a held change then merges
  ship: []                # may ship to users
agents: []                # actor ids that are agents (bots are recognised from the source)
aliases: {}               # the other ids one person has: a board email -> their GitHub login

mand init fills it from your answers to questions 3, 4 and 5.

Settings

owner

The accountable person, or people. The owner holds every right: release, go and ship. The owner's paths wait for the owner's go. List at least one person.

roles

Who else holds each right. Under release, the people who may start work that needs a release. Under go, the people whose go lets a held change merge. Under ship, the people who may ship to users.

agents

The accounts your agents act through, on the board and in git. What they do never counts as a person's word or a person's work. Bots are recognised from the source without being listed.

aliases

Another id one person has, mapped to the name your rules use for them. A person often has one id on the board and another in git.

Change it

Ben may now release work and say go, and Ann's board account counts as Ann:

owner: [ann]
roles:
  release: [ben]
  go: [ben]
  ship: []
agents: [claude-agent]
aliases:
  ann@acme.dev: ann

Only Ann may ship. Names are the ids your board and git use, or the names you map them to under aliases.