Guide
Use this guide to take SuperDomestique from a first supervised change to the
level of delegation that suits each workload. The plugin and commands are still
named faff.
Choose a path
Make a first change
Start with Your first runs. It covers initial configuration, turning an idea into tracker work, and taking one ticket through specification and implementation. Then read Adopt by change class before making any work eligible for unattended delivery.
Run work unattended
Read Adopt by change class, then Unattended runs at L3. See Why one run continued and another stopped for a paired real run. If the run needs to survive a closed laptop or disconnected terminal, continue with Run unattended work on your own machine.
Add governance to a repository
Read Commissaire for the responsibility boundary, then Add governance-check to GitHub for the repository wiring. Agent lanes explains the execution separation behind the checks.
Verify a completed run
Read Verify and read your run's evidence to check a
finished run's signed evidence with faff commissaire audit verify, find each
artifact on disk, and understand what a pass does and does not prove.
Embed Commissaire in your own repository
Read Embed Commissaire as your own governance layer to stand up Commissaire standalone (the split-key model, the runnable bare-Claude embed, and the reuser-runnable custody split) and verify your run from public key material alone.
Configure or extend the system
Configuration covers the tracker, appetite, and slots. Skills and slots explains how to replace a worker while preserving the contract. Use the CLI reference when you need a specific command.
All guide pages
| Page | For | Read next |
|---|---|---|
| Your first runs | New adopters | Adopt by change class |
| Adopt by change class | Teams deciding what agents may run | Unattended runs at L3 |
| Configuration | Repository owners setting up or tuning the plugin | Skills and slots or Unattended runs at L3 |
| Unattended runs at L3 | Teams ready to drain eligible work without scheduled supervision | Why one run continued and another stopped |
| Why one run continued and another stopped | Teams checking how an unattended run handles its gates | Run unattended work on your own machine |
| Run unattended work on your own machine | Operators providing a persistent self-hosted runner | Add governance-check to GitHub |
| Add governance-check to GitHub | Repository administrators making run checks binding | Agent lanes |
| Verify and read your run's evidence | Operators checking and interpreting a completed run's signed evidence | Embed Commissaire as your own governance layer |
| Embed Commissaire as your own governance layer | Engineers embedding Commissaire standalone in a repository with no SuperDomestique install | Add governance-check to GitHub |
| Skills and slots | Teams replacing or adding workers | CLI reference |
| Agent lanes | Integrators and advanced adopters studying execution boundaries | Commissaire |
| CLI reference | Operators and integrators looking up a command | Return to the task guide that sent you here |