Bounded harness + engineering org core
The CLI harness, scoped tools, project memory, sessions, team roles, board, independent review, and run audit are the current product foundation.
The org core is in: scoped tools, sessions, board, independent review, and replayable audit. Recent work added managed project instructions, code-aware recall, and budget-aware context. From here, the work is live local supervision, external-agent handoffs, and memory that can cross projects without leaving local control.
The CLI harness, scoped tools, project memory, sessions, team roles, board, independent review, and run audit are the current product foundation.
The desktop path is moving from a terminal grid into a live local workspace: structured run views, inline approvals, reconnectable recent work, and honest lifecycle states.
voss sync writes generated workflow docs, managed instruction sections, and editable review prompts, with a check mode for CI drift and hand-edited managed docs.
voss recall and the code_recall tool search code and project memory together, label results by source, and degrade to lexical recall when vector search is unavailable.
Long-running harness work now keeps recent context full, compresses older replay into structural summaries, and reports estimated savings from a session ledger.
Adopted tools and external CLI agents should coordinate through clear ownership, identity, and handoff signals without pretending Voss fully controls tools it did not launch.
The next memory work is curated cross-project recall first, then explicit read-only ingest for markdown docs and external memory directories.