Roadmap

Where the Open Agent Specification is headed. This roadmap is directional — proposals become real through the RFC process and repository history.

Nature

Directional

Process

RFC-driven

Bias

Implementer-first

§ 01

Horizon

Now, next, later

Roadmaps are only useful when they're honest about uncertainty. These horizons describe priorities — not guarantees or dates.

horizon · Now

01Clarify verifier rules: explicit invariants and failure modes in the contract

02Improve implementer documentation and examples

03Harden disclosure and security guidance for verifiers and issuers

horizon · Next

01Expand conformance coverage and test vectors

02Interoperability guidance for multi-method environments (bridges and adapters)

03Better tooling for reviewing and validating documents against the contract

horizon · Later

01Governance refinements driven by real implementer feedback

02Stronger formalization of edge cases and verifier behaviors

03Exploration of attestation formats where appropriate (without locking to a vendor stack)

§ 02

How priorities change

The strongest roadmap input is implementer pain: ambiguous verifier rules, hard-to-test behavior, or missing interoperability guidance.

01Implementers file issues or propose RFCs with concrete examples.

02Review focuses on verifier behavior and compatibility impact.

03Accepted changes land with documentation and conformance coverage where applicable.

Bring it to the RFC process early. The goal is a contract that stays coherent under real-world verification pressure.