Skip to main content
The harness gives one agent a bounded loop. Orchestration extends the same boundaries to a whole team: declared roles, partitioned budget, scoped tools, independent review, and a replayable trail. The promise:
Voss lets AI agents work like an engineering team while keeping every action scoped, budgeted, reviewed, and replayable.

​
The six primitives

Every run is built from the same six primitives.

​
One run, end to end

​
The MVP flow

A team is declared once in .voss, then a single goal runs as scoped, reviewed work.
This run proves the core invariants:
  • The EM cannot invent roles outside the declared roster.
  • Workers cannot write outside their assigned scope.
  • Budget cannot be oversold — it is enforced down the session tree.
  • Agents cannot mark their own work Done.
  • Done requires independent reviewer evidence.

Team config

Declare roles, scope, budget, and tools in .voss team{}.

Engineering Manager loop

The constrained tech lead that decomposes and integrates.

Board

Columns, WIP limits, and artifact-gated transitions.

Reviewers

The independent Reviewer-A / Reviewer-B split.

Session tree

Per-agent budget fan-out and durable nodes.

Principles

Engineering culture as first-class config.