Skip to content
commission

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

pageyou will be able tostatusowner
lifecycle.mdTake a task from planned to closed: claim, note, check criteria, attach evidence, close — and read every refusal along the way.writtenrelay-60
parallel.mdFan independent tasks out to several agents at once using ready, touches overlaps, and suggested batches, without collisions.writtenrelay-60
planning.mdTurn an idea into a task graph with define and apply, and re-apply a plan safely as it changes.writtenrelay-60
context.mdTrack the guidance files a task was claimed under, and detect when in-flight work is running against stale rules.writtenrelay-38

Policy and environment

pageyou will be able tostatusowner
execution-policies.mdDeclare who may execute what — preferred actor, autonomy level, required roles — and understand why approval is not completion.writtenrelay-60
workspaces.mdPrepare the place work happens (worktree, environment, ports, setup steps), with a parity table across providers.writtenrelay-60

Both capabilities have since shipped — execution policy and autonomy (relay-34), approvals as data (relay-35), and provider-neutral workspaces (relay-39relay-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

pageyou will be able tostatusowner
upgrades.mdUpgrade 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.writtenrelay-50

Adoption

pageyou will be able tostatusowner
interop.mdCoexist with a tracker that is already the source of truth: import a backlog, or bind a deliberate subset and sync it supervised.writtenrelay-58
migration.mdMove work into commission from Jira, Linear, or a markdown board, and know when to stop importing.writtenrelay-60
solo-founder.mdGo from install to “here are this quarter’s deliverables” on a real repository, running several agents.writtenrelay-61
enterprise.mdRoll commission out incrementally without displacing Jira: who owns config, how approvals map to existing review, security posture, and an exit at every stage.writtenrelay-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.