About

Roadmap

What Eva is today, and the stages that take it from a terminal client on a plugin kernel to a software factory. Each stage has an exit test it can fail.

Eva is built in stages, and each stage has an exit test it can fail. A stage is not done when it feels done; it is done when a named test stops failing.

Where Eva is today

A terminal client on a plugin kernel. A small core loads plugins, and every capability is one — the model, the surface, the trace, the themes. The plugin system, the event schema, the session store, and the cost accounting are real and shipping.

Everything else on this site describes that. Nothing here describes a stage that has not landed.

Phase I — model to agent

StageWhat it adds
0Wire. One provider, one surface, one trace. Done.
1Workflow. A pipeline that takes a Spec and returns an Outcome.
2Tools and the loop. The agent that can act, not only answer.

Phase II — agent to harness

StageWhat it adds
3Context engine. Repomap, compaction, what conditions a request.
4Environment. Workspaces, snapshots, isolation.
5Verifier. Criteria Eva checks rather than the agent claims.
6Memory and trace.
6.5Extension distribution — third parties, trust, isolation.
7Harness profiles.
8Eval harness.

Phase III — harness to factory

StageWhat it adds
9aWork items and a local scheduler.
9bControl plane and enrolment.
9cHarness adapters. Claude Code, Codex, and OpenCode, behind one contract.
9dSkills and MCP.
10Integration — the merge queue and review routing.
11Economics, dashboard, billing.
12Continual learning.

Phase IV — factory to company

StageWhat it adds
13Intent — the demand side.
14Authority and accountability.

The four "ones"

Eva's pitch is one contract, one trace, one verifier, one bill. One trace exists today. The verifier arrives at stage 5, the contract over foreign harnesses at stage 9c, and per-harness billing at stage 11.

The full plan, with the exit test for every stage, is roadmap.md in the repository.