A team that operates your data.

Supervised workers that claim, do, and verify real work across every interface, all on your own machine.

Five roles.

Each runs as a supervised worker against the one data layer.

Shipper

Picks up a defined task, does the work, and hands it off with evidence for review.

Verifier

Audits a shipper's work against the goal and either signs it off or sends it back.

Triager

Sorts inbound — leads, applicants, tasks — and routes each to the right place.

Scribe

Keeps the record straight: notes, summaries, and the audit trail of what happened.

Planner

Breaks a durable goal into the tasks the rest of the team executes against.

No agent approves its own work.

A different agent audits every change and either verifies it or sends it back. Separation of duties is enforced by the lifecycle, not by policy.

01

Todo

Work is defined

02

In progress

An agent claims it

03

Review

Evidence recorded

04

Done

A different agent verifies

An agent can never mark its own work done — a different agent has to verify it first.

Shipper

Picks up a defined task, does the work, and hands it off with evidence for review.

Verifier

Audits a shipper's work against the goal and either signs it off or sends it back.

Triager

Sorts inbound — leads, applicants, tasks — and routes each to the right place.

Scribe

Keeps the record straight: notes, summaries, and the audit trail of what happened.

Planner

Breaks a durable goal into the tasks the rest of the team executes against.

Orchestrator01

Allocates the lane bank across every active goal and spawns a manager per goal.

Manager02

Owns one goal — fans shippers and verifiers across lanes and merges verified work.

Worker03

Leases a lane and ships one task in its own isolated worktree, then frees the lane.

×N lanes

Each worker runs in its own isolated git worktree, so dozens operate your data concurrently on one machine. Promotion to your main branch stays human-gated.

Wired into the operation.

Durable goals & autopilot

Give the team a goal and it pursues it within a budget you set. An autopilot tick picks up matching work and reaps stale claims. Everything is off by default with a master kill switch.

The Crucible — self-optimizing

Every agent action is measured. An optimizer drives each workflow toward the cheapest version that still passes — eval-driven, gated, with a self-healing rollback. They get cheaper and better over time.

Copilot operates and builds

The same chat can run your workspace through MCP tools and, when you allow it, edit the product's own source — through the same ship / verify gate, with every develop turn revertible.

A signed audit trail

Lens logs every run: what ran, which tools it called, what it touched, and what it cost. The event log is a per-node hash chain with signed checkpoints — tamper-evident by construction.

Open to your terminal

An MCP server exposes every operation to any MCP-aware agent — including the Claude you already run in your terminal. The same gate applies whether work comes from the UI or a worker.

Put the team to work.

Download Excellent and your agent roles come online against a database on your machine.