Roadmap · shipped · next · declined

Shipped, next, and declined

Commission is planned and executed in Commission. This page is that task graph, read out — not a summary of it, and not a list somebody remembered to update.

Every row below is a real task. commission show <id> prints the one you are looking at, with its acceptance criteria, the evidence attached to it, and the notes the sessions that worked it left behind. Nothing here is written by hand: scripts/roadmap.ts reads the database and this page renders what it emitted.

There are no dates on anything that is not already closed, and there are no quarters. No release has been cut and there is no schedule to publish; a roadmap with a timeline on it would be the first thing on this site that could not be checked.

76: closed; tasks with status done, grouped by the day of closed_at, newest first
4: in flight; tasks held in in_progress or in_review right now
4: workable now; open tasks whose every dependency is closed — the same predicate commission ready evaluates, computed at read time rather than stored
3: waiting on a dependency; open tasks with at least one dependency still open; blocked is derived from those dependencies and is never a status anybody set

87 tasks in the graph, 0 cancelled. First closed 17 July 2026, most recent 27 July 2026. Snapshot taken 27 July 2026.

Shipped

What exists today

Closed tasks, newest first. A task is only closed when its acceptance criteria are ticked and the evidence its gate requires is attached — Commission refuses otherwise, including for its own work.

27 July 2026

51 closed

relay-66 Pricing and roadmap pages
relay-65 Documentation site rendered from docs/
relay-83 What the dashboard still needs before it leaves beta
relay-82 The inbox deserves the most care: it is what a human actually opens
relay-84 A gate is satisfied by evidence that says 'pending'
relay-81 Dashboard chrome: bring the language in without importing the marketing page
relay-63 Diagrams: intent → Commission → humans / AI / GitHub / Jira / CI / deploy
relay-80 One design language, two consumers: share tokens with the dashboard
relay-76 Pricing tiers and purchase flow, scaffolded
relay-75 Visual identity and motion: make the landing page feel alive
relay-79 commission apply does not remove dependency edges it no longer declares
relay-78 commission init tells you to set COMMISSION_ACTOR, which makes you not-a-human
relay-77 MCP is a first-class surface: prove the whole loop runs over it
relay-61 Adoption paths: solo founder, enterprise, architecture, contributing
relay-73 Web inbox: wire 'answer' to relay-44's answer() instead of writing a note
relay-64 Site content: hero, why, execution model, human+AI, solo, enterprise, features
relay-74 commission init should declare the human who ran it as an actor
relay-48 Final CLI audit against the contract
relay-60 Guides: lifecycle, execution policies, workspace, context, integrations, migration
relay-59 Core documentation: installation, configuration, CLI, MCP, HTTP API
relay-68 Every refusal audited: what is missing, and how to fix it
relay-57 Land the licensing decision in the repository
relay-45 Human surfaces in the web view: inbox, approvals, standup
relay-28 Context bundles get an explicit token budget and declared omissions
relay-47 First-run experience and discoverability
relay-44 commission ask — agents escalate decisions instead of guessing
relay-71 Technical page: move the operator-facing detail off the landing page
relay-43 commission inbox — 'what needs my judgment?'
relay-29 Optimistic concurrency for edits (--if-version)
relay-42 GitEnv as the best-supported provider (never required)
relay-38 Drift detection, staleness warnings, and local-only overrides
relay-37 Context tracking and fingerprints
relay-36 Explainable routing — why this actor, and suggested delegations
relay-41 Environment providers — dotenv, exec, Doppler, 1Password, Vault
relay-50 Database migrations, upgrade validation, and backup guarantees
relay-35 Human approval as data — distinct from technical completion
relay-40 Worktree strategy, port allocation, setup/teardown hooks
relay-32 Deprecation notice policy for pre-versioned config
relay-34 Task execution policies — preferred actor, autonomy, who may execute
relay-33 Actor registry — humans and agents as declared, first-class identities
relay-62 Astro site scaffold, design system, dark mode, typography
relay-39 Provider-neutral workspace interface
relay-27 Claims as a first-class lease, separate from assignee
relay-56 Pricing, tiers, and the open-vs-closed source recommendation
relay-46 CLI surface contract: naming, help, flags, exit codes — enforced by test
relay-58 Documentation architecture and authoring conventions
relay-49 Versioning, changelog, and compatibility policy
relay-55 Competitive research: where Commission actually sits
relay-31 commission config — show, validate, explain, init, migrate
relay-54 Positioning and messaging system
relay-30 .commission.json — canonical project configuration, strict and versioned

17 July 2026

25 closed

relay-26 Demote Jira/sync out of the pitch and README
relay-25 Supervised chaos pass: hunt sync/plan breakage in sandboxes
relay-24 Plan emission must compare claim-equivalence, not status names
relay-23 Jira-safety test hardening: site-mismatch, plan scoping, verb invariant
relay-22 Jira components → touches: informed parallel batches for imported tasks
relay-21 Isolation gates: integrations as allowlist + repo-level .commission.json config
relay-20 Work-selection policy: severity, due dates, sprints, rank
relay-18 Sync M4: continuous — serve --sync poll, auto-close policy, standup divergences
relay-19 README tour: mention standup and sync in the 90-second tour
relay-17 Sync M3: outbound plans + executors — agent-executed Jira writes
relay-16 Sync M2: pull + canonicalize — signals beat claims, divergences recorded
relay-15 Sync M1: bindings — schema, bind/unbind/branch, auto-binding adapters
relay-14 Standup script: since-last-standup window + speakable narrative
relay-13 Standup day digest + scalable nav + live refresh
relay-12 Web UI polish for humans: fix font escaping bug, humanize events, reduce agent noise
relay-7 Touches-aware dispatch hints in ready output
relay-5 Markdown export: git-committable board snapshot
relay-10 serve: detect stale server (running code older than source)
relay-4 GitHub auto-evidence: merged PR attaches itself
relay-11 Web UI readability + navigation pass
relay-1 MCP server over core
relay-3 Define-project flow: idea → vision + task graph
relay-2 Jira adapter: mirror day-job issues into a local board
relay-9 Adopt external review findings: leases, plan keys, event cursors, reasons, doctor
relay-8 Standup view: brief done/doing/blocked narrative for humans

What is not built yet

The frontier, as Commission computes it. Nothing in this section exists; every line is work that is open or in hand, and none of it carries a date.

In hand right now

Claimed and being worked, by a person or by an agent holding a lease.

relay-51 in progress

Cross-platform binaries: macOS, Linux, Windows
relay-67 in progress

Site deployment pipeline
relay-72 in review

Landing page for buyers: outcome first, human surface, no CLI
relay-85 in progress

Corrected evidence is indistinguishable from the value it corrects

Workable now

Open, with every dependency closed. Any agent running commission next --claim would be handed one of these.

relay-6

Hosted deploy story
relay-69

Repository-wide polish pass
relay-86

A cancelled task is invisible on the board
relay-87

Commission becomes Charter

Waiting on something else

Blocked, and blocked is derived from the dependencies below rather than set by anyone — so it cannot be stale and it cannot be wrong.

relay-52

Distribution: GitHub Releases, install script, Homebrew tap, npm

needs relay-51
relay-53

Container images for commission serve

needs relay-51
relay-70

Cut Commission RC1

needs relay-69 · relay-52 · relay-53 · relay-67 · relay-87

That is the whole open frontier — not a selection from it. Commission's distribution, hosting and licensing work is on it, which is why every paid tier on the pricing page says plainly that it cannot be bought yet.

Declined

What Commission has decided not to do

Each of these is a decision, not a gap. If a request lands in this list the answer is “no, and here is why” — not “not yet”.

Estimation: Story points and human-guessed durations are the least reliable
A settable blocked status: Blocked is derived from dependencies. A status that
A status taxonomy: Five statuses, moved only through transitions with explicit
Freeform status writes: Nothing can write a status except a transition, so
Silent automation: Commission never pushes to an external system unattended, never
Two-way sync as a way of life: Interop is an adoption bridge — import and stop,
Agent-satisfiable human approval: When approvals ship, an agent attempting to
Inference about intent: Configuration is deterministic: a strict schema,
Being the interface humans work in: The web view is read-only by design.

Read out of docs/positioning.md §7.2 by the same script that read the task graph, so this page cannot quietly soften one of them.

And what is never sold, at any tier

The commercial half of the same list. These are commitments the business model makes explicitly, and they hold at every tier including the ones that are not open yet.

A cap on work, projects or agents
Anything that slows agents down when you run a lot of them
A prepaid balance that stops work when it hits zero
A charge for finishing something
Required reporting back to us from software on your machine
Holding your data hostage — export works at every tier, always

Checking this page

How to catch it being wrong

A roadmap that drifts from the tracker, on the tracker's own website, would be the most damaging page on this site. So it is generated, and here is how to prove it.

Every id here resolves. Every closed task has evidence attached to it, because Commission refuses done without it. Every blocked task names the tasks it is blocked by, and those are the rows the dependency is actually stored in — not a label somebody typed.

The one thing this page cannot promise is freshness: it is a snapshot taken when the site was last built, and it says at the top when that was. Regenerating it is one command, and the build ships whatever the command last emitted.

bun run roadmap
re-derives this page from the database, read-only
commission show <id>
the task behind any row, with its criteria and its evidence
commission ready
the same frontier "workable now" is derived from

Commission is proprietary software and the repository is private, so those commands are ones the people building it run, not ones you can run against this graph yet.