Open specification
Help set the standard
The spec is stewarded today with an explicit goal: community governance as the contributor base forms. The highest-value feedback is an implementation report — you tried to build against ADL and hit friction.
The structured intake template lives at .github/ISSUE_TEMPLATE/open-spec-review.md in the spec repo. If the repo 404s, the public flip is imminent — try again shortly, or grab the spec from the downloads on the spec page.
Classify your feedback: the five-word status vocabulary
Every surface in the spec carries one of five state classifications, and the review template asks you to pick one. Using the same words keeps claims honest on both sides.
stable
Specified, schema-checked, and covered by conformance tests.
experimental
Specified but still expected to change on feedback.
report-only
Mapped and diagnosed, but not executed — compatibility reports, not runtime claims.
executable prototype
Runs locally under fail-closed constraints (e.g. x402-dry-run).
future work
Named but not built. Anything mainnet-facing lives here until externally audited.
Open gaps we want challenged
These are the known weak points of v0.2.0-beta. Feedback that attacks them — especially with a reproduction or a proposed schema — moves the spec fastest.
- Charge-side conformance enforcement — the seller side of payment intent is specified more loosely than the buyer side.
- Price discovery — how buyer agents compare quotes across sellers is not yet standardized.
- Session caps — per-session spend limits beyond the single-delegation cap.
- Output schemas — machine-checkable contracts for what a paid delegation returns.
Where next
Read the spec, check what has shipped, then tell us where it breaks.