Skip to main content

autonomous delivery / evidence first

Intent in.
Evidence out.

autodev is a planning board, delivery fleet, and local operator workspace for software work. It turns typed stories into reviewed, gated changes—and records the facts used along the way.

Get started Follow a delivery

Pre-release · Open source · Rust · agent-harness agnostic

delivery / candidate evidence required
  1. 01
    PlanTyped stories define intent, scope, dependencies, and proof expectations.
  2. 02
    DispatchWorkers operate in isolated worktrees through a configured agent bridge.
  3. 03
    ProveRepository-level evidence and a separate review turn evaluate the result.
  4. 04
    LandIntegration and the post-merge gate run before the board advances.
intentobserved facts

01 / Contract

Autonomy is only useful
when its claims are inspectable.​

A worker saying “done” is not delivery. The fleet is designed to observe the commit, check repository-level evidence, run a separate review turn, integrate on the current tip, and gate the resulting tree before advancing the plan. Current gaps are documented explicitly.

02 / Invariants

Built to leave a trail.​

The rules behind every transition from a plan to a landed change.

Observe, never trust

Commits come from git. Effects are re-read from storage. Usage is recorded by the harness or stays unknown.

Read the principle

Absence stays absence

Unknown never quietly becomes zero, and aggregates carry the denominator that gives them meaning.

Read the principle

Proof is the invariant

It is the project contract. The current pre-release enforcement gaps are disclosed openly.

Read the principle

03 / At the CLI

The control loop,
in the open.​

Check the plan, run a bounded drive, then investigate what the fleet recorded. These are real commands—not a staged transcript or a promise of a particular result.

Browse the complete CLI

  1. Check the contract

    autodev board check

    Validate planning files, vocabulary, story contracts, and references before work can move.

    Plan a board

  2. Drive a bounded loop

    autodev fleet drive --ticks 60 --interval 5

    Run the reconciler until it becomes quiet or reaches the explicit tick limit.

    Operate the fleet

  3. Open the operator workspace

    autodev serve

    Inspect the board, fleet, diffs, workflows, conversations, connectors, and requests over loopback.

    Use the workspace

No sample output is shown. Results depend on the repository, configuration, and persisted fleet state.

04 / Start

Put your plan under test.​

Start with the board alone, then add the fleet when your repository contracts pass.

Read the quickstartExplore the source