Roadmap - Voss Docs

Voss started as a bounded single-agent harness. It is now an agent engineering organization layer built on top of that substrate. The org core is in, the harness has code-aware recall and budget-aware context, and the desktop workspace is still being verified for live local supervision.

Shipped

The bounded harness substrate, engineering-org core, and current recall/context work:

Area	What shipped
Harness	Plan/edit/auto modes, scoped writes, resumable sessions, project memory, the `.voss` language
Capabilities	A normalized, permissioned capability registry — `voss capabilities list` / `inspect`
Principles	First-class engineering principles — `.voss/principles.yml`, `voss principles show`
Team config	`.voss team{}` roster with compile-time scope/budget containment — `voss team check`
Session tree	Durable per-agent nodes with budget fan-out — `voss session tree`
Board	The board state machine with WIP limits and gated transitions — `voss board`
Reviewers	The independent Reviewer-A / Reviewer-B split — `voss review`
EM loop	The Engineering Manager loop — `voss team run` composes the whole run
Managed instructions	`voss sync` for generated workflow docs, managed instruction sections, editable prompts, and `--check` drift gates
Semantic recall	`voss recall` and the `code_recall` tool search code and project memory with source labels and BM25 fallback
Budget-aware context	Conservative context packing, `--no-pack`, `token-savings.jsonl`, and `/cost` estimate output

In verification

Area	Goal
Live desktop workspace	Structured panes, inline approvals, reconnectable recent work, and honest live/disconnected states
SDK proof suite	Internal proof that Python, TypeScript, Go, and Rust consumers can drive `voss serve` before SDK surfaces are promoted as primary public workflows

Planned

Area	Goal
External-agent handoffs	Ownership claims, identity, handoff signals, and review-request conventions for agents Voss observes but does not fully control
Global memory	Curated cross-project recall under the user’s local Voss home, with explicit promote/forget/vacuum commands
External memory and docs ingest	Read-only ingest for configured markdown corpora, labeled as derived recall sources
TUI and voss-app autonomous proof	End-to-end driving of the interactive surfaces through internal proof runs

Deferred

Hosted SaaS control plane and accounts
Distributed, multi-machine agent swarms
Autonomous deploy / delete / migration / money actions without human sign-off
Voss as a general-purpose programming language

The roadmap stays local-first. Documentation should not claim more safety or completeness than the shipped surface proves.

June 12, 2026Semantic code recall, budget-aware context, managed sync checks, and SDK proof-suite work.