Guides
You will be able to find the one narrative page that matches what you are trying to do today, and follow it to a finished, verified outcome.
Guides are task-shaped and opinionated: each one names a goal, walks the whole path, and ends with the exact command sequence. Where a guide needs an exhaustive list of flags or fields, it links to Reference rather than restating it — restated tables are the ones that rot.
The working loop
| page | you will be able to | status | owner |
|---|---|---|---|
lifecycle.md | Take a task from planned to closed: claim, note, check criteria, attach evidence, close — and read every refusal along the way. | written | relay-60 |
parallel.md | Fan independent tasks out to several agents at once using ready, touches overlaps, and suggested batches, without collisions. | written | relay-60 |
planning.md | Turn an idea into a task graph with define and apply, and re-apply a plan safely as it changes. | written | relay-60 |
context.md | Track the guidance files a task was claimed under, and detect when in-flight work is running against stale rules. | written | relay-38 |
Policy and environment
| page | you will be able to | status | owner |
|---|---|---|---|
execution-policies.md | Declare who may execute what — preferred actor, autonomy level, required roles — and understand why approval is not completion. | written | relay-60 |
workspaces.md | Prepare the place work happens (worktree, environment, ports, setup steps), with a parity table across providers. | written | relay-60 |
Both capabilities have since shipped — execution policy and autonomy (relay-34),
approvals as data (relay-35), and provider-neutral workspaces (relay-39–relay-42)
are all done, and positioning.md §8 lists them under shipped since this document
was first written. Where a sub-feature is declarable in configuration but not yet
enforced, the page says so in place rather than describing it in the present tense.
Running commission
| page | you will be able to | status | owner |
|---|---|---|---|
upgrades.md | Upgrade commission over a database that holds real work: check what is pending before you do it, read the automatic backup, and restore if it goes wrong. | written | relay-50 |
Adoption
| page | you will be able to | status | owner |
|---|---|---|---|
interop.md | Coexist with a tracker that is already the source of truth: import a backlog, or bind a deliberate subset and sync it supervised. | written | relay-58 |
migration.md | Move work into commission from Jira, Linear, or a markdown board, and know when to stop importing. | written | relay-60 |
solo-founder.md | Go from install to “here are this quarter’s deliverables” on a real repository, running several agents. | written | relay-61 |
enterprise.md | Roll commission out incrementally without displacing Jira: who owns config, how approvals map to existing review, security posture, and an exit at every stage. | written | relay-61 |
What makes a guide finished
- It opens with one sentence saying what the reader will be able to do.
- It states its audience and what it assumes you already did.
- It ends with the complete command sequence, uninterrupted, ready to paste.
- Every one of those commands is executed by a test.
- It links to Reference for exhaustive lists, and to
positioning.md§6 for vocabulary — it defines no term itself.
This page is docs/guides/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.