Roadmap

Status: v0.1 implemented and published to npm (all acceptance criteria green, including the MCP adapter — it did not slip). Five packages live under @orpc-agent/* at 0.1.0 (Q1 resolved). Scope commitments below are firm.

Now — v0.1 "Governed core" (published)

The smallest coherent release proving the thesis: define a capability once, expose it through multiple governed surfaces.

• @orpc-agent/core — capability metadata + registry, 15-stage runtime, policies, in-memory approvals with input-hash binding, structured errors, audit events, tracing interface, timeout/cancellation, eligibility-gated retries, Zod v4 JSON-Schema conversion
• @orpc-agent/ai-sdk — AI SDK v5 tools over the runtime
• @orpc-agent/testing — deterministic governance testing, no LLM required
• @orpc-agent/opentelemetry — tracing adapter
• @orpc-agent/mcp — MCP server adapter (final increment; slips to 0.2 rather than delaying the release)
• examples/customer-support — the reference application (one read flow, one approval-gated write flow, and the full governance suite)

Definition of done: the acceptance criteria. Increment plan: milestones.

Next — v0.2 "Durability seams" (planned, order by demand)

• Persistent approval-coordinator reference implementation (Postgres) — or recipes-only, per Q8
• First workflow-engine adapter for the workflow surface (Temporal / Inngest / Trigger.dev — Q7)
• MCP: dynamic list_changed; elicitation-based confirmation prototype behind a flag (Q4)
• Community schema-converter adoption for Valibot/ArkType (Q3)
• API stabilization pass: experimental → stable for core definition APIs

Later — exploratory (no commitment)

• Streaming (event-iterator) capabilities with per-chunk governance semantics (Q11)
• Framework-level rate limits/quotas (Q9)
• Declarative policy input constraints (Q6)
• Capability inventory/report tooling (CI surface-diff action)
• Metrics emission; additional adapters (CLI, A2A) — each begins as a design doc against the adapter contract

Non-goals (permanent)

These are boundaries, not backlog (overview):

• Agent loops, planners, prompt management, memory stores
• A workflow engine, scheduler, or job queue of our own
• Bundled databases for approvals or audit
• Authentication/authorization providers
• UI frameworks or hosted dashboards
• Exactly-once execution claims
• Support for non-oRPC procedure systems in core

How this roadmap changes

Scope moves between tiers only via ADR (for architectural shifts) or maintainer consensus recorded in GOVERNANCE.md. Open questions graduate here when resolved; nothing ships to "Now" while its blocking question is open.

---

Related: implementation milestones · open design questions.