Orchestration overview

The six primitives

Every run is built from the same six primitives.

Primitive	Meaning	Where it lives
Capabilities	The agent toolbelt — typed, permissioned, auditable	`voss capabilities`
Principles	Engineering culture injected into every agent	`.voss/principles.yml`
Orchestration	Delegation and integration	Engineering Manager loop
Roles	Specialist lenses with their own scope and budget	`.voss team{}`
Memory	Institutional knowledge across runs	Session tree, project memory
Verification	The independent review loop	Reviewer A/B

One run, end to end

human idea
  -> EM derives cards
  -> assign roles from the declared roster
  -> partition budget down the session tree
  -> dispatch workers in parallel (within WIP limits)
  -> Reviewer-A authors the bar from the idea
  -> Reviewer-B judges narrative-blind
  -> board gates Done on independent review
  -> RunFinal record + review sidecars persisted

The MVP flow

A team is declared once in .voss, then a single goal runs as scoped, reviewed work.

voss team check
voss team run "Add password reset flow with tests"
voss board
voss review latest

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.

​The six primitives

​One run, end to end

​The MVP flow