This is the public roadmap. It is honest about what ships now, what is next, and what is further out. Nothing moves to planned without an approved governing spec.
Run capabilities at the edge. Same WASM binary, same contract. Cloudflare Workers and similar targets in scope.
executor / edgeCall Traverse capabilities from Python. Useful for data pipelines, ML workflows, and teams that do not write Rust.
sdk / pythonMore expressive queries against trace artifacts. Filter by capability, outcome, contract clause, and time range. CLI and MCP both benefit.
tracing / cliReal numbers for real workloads. Contract validation overhead, execution latency by environment, and comparisons against baseline approaches.
docs / perfMore working examples beyond Expedition. Pricing rules, eligibility checks, validation pipelines. Each one governed by a spec and fully tested.
examplesNative cloud deployment for capabilities. AWS Lambda and similar targets. The same binary that runs in browser or at edge, now in cloud.
executor / cloudFirst-class support for capabilities that run inside AI pipelines as governed tools. Builds on the MCP foundation with richer placement declarations.
ai / placementCoordinate multiple agents calling governed capabilities. Conflict prevention via contract constraints. No two agents can violate the same rule in the same execution.
ai / orchestrationVisual interface for exploring capabilities, their contracts, and trace history. Designed for teams that need to audit what ran and why.
observabilitySoftware bill of materials for capabilities. Know exactly what is in each WASM binary, what contracts govern it, and what versions are in production.
security / sbomRun capabilities on-device. Mobile and embedded targets. The portability story extends all the way to the hardware layer.
executor / deviceOpen an issue on GitHub. A clear problem statement and a proposed spec is the fastest path to getting something on the roadmap.