UAIX has expanded UAI-1 again by publishing the operating surfaces that usually stay implicit in early protocols: transport bindings, trust-channel guidance, a public error registry, and a conformance ladder for support claims.
What changed
- UAI-1 now explains how the protocol fits beside A2A, MCP, W3C Trace Context, RFC 9457 problem details, and VC-based trust layers instead of leaving that boundary as a vague future note.
- Tools and the 验证器 now expose machine-readable transport, trust, error, and conformance routes alongside the existing catalog, schemas, registry, examples, and validate surface.
- The current 示例 and 模式 now show capability records and conformance records that point back to those operating-surface artifacts.
- Implementations and the public release trail can now describe support claims more precisely because the conformance ladder is published instead of implied.
How to use this update
- Use UAI-1 for the normative boundary and the new adjacent-protocol fit explanation.
- Use Tools when automation needs the live route family, and use the 验证器 when a human needs the workbench plus issue export.
- Carry the new transport, trust, error, and conformance records beside 模式, 示例, and validator output whenever you are evaluating interoperability or support claims.
- Use the 变更日志 and News archive together when you need the durable release record for these new surfaces.
Why this matters
Protocols become much more usable when they answer how messages travel, how trust is expressed, how failures are named, and what a support claim actually means. This update moves UAI-1 closer to that bar and makes the public record stronger for both people and automation.