The roadmap is capability-driven. Dates are intentionally omitted until maintainer capacity and public adapter evidence are available.
- Protocol vocabulary and execution state machine
- Provider SPI and capability manifests
- Capability-based routing and bounded fallback
- Provider-local concurrency and queue admission
- Usage facts without customer billing
- Deterministic mock provider and conformance runner
- Loopback HTTP/SSE server and TypeScript SDK
- Public-data scan and GitHub Actions workflow template
- Activate the GitHub Actions workflow after an authorized credential has workflow scope
- Runtime schema validation generated from the normative specification
- Idempotent execution creation
- Explicit asynchronous submit/status/result lifecycle
- Durable event-store SPI and resumable SSE cursors
- Retry budgets and richer cancellation conformance
- OpenTelemetry GenAI semantic-convention mapping
- Threat model for shared data-plane deployments
- One typed synchronous/SSE model provider
- One content-block/tool-stream provider
- One asynchronous media-task provider
- Public-documentation evidence registry per adapter
- Sanitized contract fixtures and adapter-specific conformance suites
- Go client SDK
- Python client SDK
- Optional sidecar packaging
- Gateway integration example with authentication remaining outside the runtime
- Versioned capability catalog and model-discovery experiment
These are not part of the completed v0.1 contract:
- production durable EventStore implementations and distributed flow-control coordination;
- live-account provider certification and scheduled model-radar ingestion;
- stable package-registry publication after API feedback;
- authenticated hosted gateway, tenant control plane, or customer billing.
- Customer wallets, payments, invoices, discounts, taxes, or exchange rates
- A hosted model marketplace or public SaaS control plane
- Copying private provider configuration, production traffic, or proprietary routing policies