Back to home
Roadmap · v0.4.0 focus

From terminal helper to verifiable delegation

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.

Nowv0.4.0

Trust foundation

Project Memory, MCP tools, and a verified agent loop become one release stream.

Remembers project contextConnects external toolsShows a clear work trailDoes not finish code work without evidence

The path to 1.0

Each step raises the level of trust before adding more autonomy.

v0.4.0Current focus

Trust foundation

Project Memory, MCP tools, and a verified agent loop become one release stream.

Remembers project contextConnects external toolsShows a clear work trailDoes not finish code work without evidence
v0.5Next

Visible proof

The user should see what changed, what ran, what passed, and what still carries risk.

Evidence bundleDiff reviewFirst-run polish
v0.6Then

Living project knowledge

Memory becomes maintained knowledge, not a pile of notes.

Memory updatesStaleness checksProvenance
v0.7After trust

Background delegation

Tasks can live longer than one open terminal and stay isolated in their own workspaces.

Task modelGit worktreesAttach and resume
v0.8 → 1.0Stabilize

Delegation with judgment

SOBA should turn outcomes into contracts, escalate when risk is high, and ship with a stable user promise.

Verification contractsSmart escalation1.0 release hardening

What stays constant

The order may change as the project learns, but these product promises should not.

Verify before confidence

A green answer should be backed by visible work, commands, evidence, or a clear unverified status.

Extensible, not chaotic

MCP and skills expand the toolset while the runtime keeps permissions and results understandable.

Long work without context rot

Sessions, capsules, checkpoints, and memory should preserve the task state across long work.