Goal

Get from "API endpoints exist" to "user submits task → agents execute → results come back" — the minimum viable runtime that a web UI (or any client) can drive.

Current State

The infrastructure layer is complete: REST API (Litestar), auth (JWT + API key), WebSocket channels, config loading, persistence (SQLite), Docker, CI/CD. The agent internals are complete: execution loops (ReAct, Plan-and-Execute), provider layer (LiteLLM + routing + resilience), budget tracking/enforcement, security (SecOps, rule engine, output scanning, trust), communication (message bus, delegation, conflict resolution, meetings), HR (hiring, performance, promotions), tools (file system, git, sandbox, code runner, MCP bridge).

What's missing is the runtime wiring — the coordinator that ties agents, tasks, and the API into a running system.

Critical Path (dependency order)

These 3 issues are the only blockers to a functional end-to-end flow:

• feat: implement concrete memory backend adapter #206 — Concrete memory backend (Mem0 adapter) — agents need memory to function across turns. All protocols/retrieval pipeline exist, just needs the adapter.
• feat: implement centralized single-writer state coordination (TaskEngine) #204 — TaskEngine (single-writer state coordination) — the central coordinator that owns task lifecycle. API controllers need this to create, assign, and track tasks. Currently there's no single writer — tasks can be mutated from multiple places.
• feat: wire runtime multi-agent coordination #205 — Wire runtime multi-agent coordination — connects AgentEngine + TaskEngine + MessageBus + config loading into a running system. This is the "boot a company from config and start processing" glue.

Stretch (not blocking, but high-value for demo)

• feat: implement approval workflow gates in engine #258 / feat: implement request_human_approval tool for approval workflow #259 — Approval workflow gates + tool — enables "agent wants to do X, approve?" in the UI. Without it, agents run fully autonomous (acceptable for initial demo).
• feat: implement checkpoint recovery strategy #201 — Checkpoint recovery — without it, a crash loses in-progress work. Acceptable for demo, not production.
• feat: implement web UI dashboard #233 — Web UI dashboard — the actual Vue frontend. Can start with API-only or a quick prototype.

Definition of Done

With the critical path complete, this flow works:

1. Load a company config (YAML)
2. POST /api/v1/tasks creates a task
3. TaskEngine assigns it to an agent via routing
4. Agent executes (ReAct loop → LLM → tools → memory)
5. Results flow back via REST + WebSocket
6. Budget, security, and HR systems track everything

That's 0.2 — a runtime you can build a UI on top of.