Start here
You will be able to install commission, put one real task through it end to end, and hand that loop to a coding agent — in about ten minutes, on a repository you already have.
This section is read in order, once. Everything else in the documentation assumes you have done it.
Pages
| page | you will be able to | status | owner |
|---|---|---|---|
install.md | Install commission by any of its supported paths, and verify the install with a single command. | written | relay-59 |
first-task.md | Create a project, plan a small graph, claim a task, hit a refusal, satisfy it, and close the task. | written | relay-59 |
first-agent.md | Point a coding agent at commission so it claims, records, proves, and closes without you narrating the state. | written | relay-59 |
next-steps.md | Choose the one guide that matches what you are actually trying to do. | planned | relay-61 |
What the first-task page has to demonstrate
Not a tour — a loop that ends somewhere real. The page is only finished when a reader has:
- created a project and seen
.commission.jsonappear in the repository; - created more than one task with a dependency, so the ready frontier is visibly smaller than the backlog;
- run
commission next --claimand read a context bundle; - run
commission doneand been refused, then read the refusal and followed the exact command it named; - run
commission doneagain and had it succeed.
The refusal is the point. A getting-started page that only shows the happy path teaches the wrong model of the product: it hides that completion is a checked fact rather than an assertion.
Conventions this section must follow
Every command block is copy-pasteable in order from a clean checkout, and every one of them is executed by a test — see Contributing → documentation. Getting-started prose that has drifted from the binary is worse than no getting-started prose, because it is read first and trusted most.
Related
- Guides — once the loop makes sense, the task-shaped material.
- Reference → CLI — every command, generated from the command tree.
- Concepts — why the loop is shaped this way.
This page is docs/start/index.md in the Commission
repository, rendered in place — the site keeps no copy of it. The repository is private, so there is no edit link to follow.