Phases 12–13 — Shipped
Standalone adoption and evidence-first execution quality
Install surface, first-run UX, examples, docs, compatibility policy, release workflow, structured recovery, approvals, and auditable artifacts. All shipped.
Roadmap
Build the product around operator trust, not feature theater.
Agent Harness is not trying to become a vague “AI platform.” The current program is tighter: standalone adoption, reliable execution, benchmarkable quality, and only then careful expansion toward shared operation.
Current stance
No hosted plan, no checkout flow, no account gate in this cycle.
The website is here to help users install, evaluate, and understand Agent Harness as a standalone OSS product. Commercial packaging and hosted control-plane concerns are deliberately deferred.
Phase 14 — Current
Retrieval, routing, and benchmark quality
Treat routing and semantic-context improvements as benchmarkable product work instead of intuition or anecdote. Eval loops, routing evidence, and persisted comparison reports.
Phase 15 — Next
OSS-first expansion toward team operation
Prepare for shared-controller usage without turning the standalone local path into a second-class experience.
Later
Hosted control plane and commercial packaging
Remote controller, auditable operator actions, storage abstraction for persistent DB backends. Deliberately deferred until standalone is solid.
Want the concrete details?
The docs site summarizes the product story. The repository roadmap and compatibility notes hold the implementation-level commitments.