UAIX has moved UAI-1 from a thinner message format into a more operational public exchange contract with a richer shared envelope, a published field registry, better async workflow coverage, and stronger validator-backed evidence.
What changed
- UAI-1 now explains the current common envelope more directly, including conversation state, delivery semantics, trust metadata, provenance, integrity, and extensions.
- Schemas, Registry, and Examples now publish six current profiles, including
uai.task.status.v1for async work and stronger typed error handling. - The public field registry now keeps keyed JSON, keyless transport order, and nested body order aligned across the current release.
- Tools and the Validator now describe the route family and policy checks more clearly so the public record is easier to automate against.
How to use this update
- Start on UAI-1 for the new envelope and boundary description.
- Use Schemas, Registry, Examples, and the field registry together when evaluating compatibility.
- Use the Validator to turn that updated contract into reviewable conformance evidence.
- Carry any release-facing support claim through Implementations and the Changelog so the broader public record stays aligned.
Why this matters
UAIX becomes more credible when the standard explains real workflow state, trust hints, field order, and conformance evidence on the public record instead of leaving those details as future work or local convention. This update is a substantial step toward making UAI-1 a practical public coordination layer for AI-to-AI systems.