Trust foundation
Project Memory, MCP tools, and a verified agent loop become one release stream.
This roadmap shows product intentions, not internal task cards. The direction is simple: SOBA should remember the project, use the right tools, verify its work, and know when to ask.
Project Memory, MCP tools, and a verified agent loop become one release stream.
The path to 1.0
Project Memory, MCP tools, and a verified agent loop become one release stream.
The user should see what changed, what ran, what passed, and what still carries risk.
Memory becomes maintained knowledge, not a pile of notes.
Tasks can live longer than one open terminal and stay isolated in their own workspaces.
SOBA should turn outcomes into contracts, escalate when risk is high, and ship with a stable user promise.
What stays constant
A green answer should be backed by visible work, commands, evidence, or a clear unverified status.
MCP and skills expand the toolset while the runtime keeps permissions and results understandable.
Sessions, capsules, checkpoints, and memory should preserve the task state across long work.