Local-first harness
Voss runs from the developer's machine, keeps provider credentials local, and treats shell/file access as explicit permission surfaces.
Product shape
Four pieces, one boundary model.
Engineering org loop
The orchestration layer models work as tickets, reviewers, audits, and handoffs instead of a single agent improvising in a repo.
.voss control language
Project instructions, roles, budgets, principles, and gates are declared in source-controlled workflow files.
Replayable evidence
Plans, diffs, tests, review verdicts, blocked work, and residual risk are kept in the run trail so claims can be checked.
Intent
Keep automation inspectable.
Voss is built around a simple premise: an agent can be useful only when its authority is legible. The product keeps the human-facing parts of engineering work intact - plans, scopes, budgets, reviewers, tests, and sign-off - then gives agents a runtime that respects those boundaries.