UAIX has tightened the public developer onramp and protocol-fit story so first-time readers can tell what UAI-1 is, how it relates to MCP and A2A, and what is actually published today.
What changed
- The homepage now describes UAI-1 as the public envelope, trust, and evidence layer for interoperable AI exchange instead of leaving the boundary implicit.
- Get Started now includes a faster developer path, a clearer current developer kit, and an explicit note about what is not yet published as public support.
- UAI-1, Governance, 引用 and Contributors, and Press now explain more directly how to position UAIX next to MCP, A2A, and adjacent runtime systems without overselling current maturity.
How to use this update
- Start on Home and Get Started when you need the quickest answer to what UAIX is and what a first proof run looks like.
- Use UAI-1 when you need the explicit protocol-fit explanation and the boundary between the public record and runtime-specific tool flows.
- Use 引用 and Contributors and Governance when you need the clearest current answer on ownership, review posture, and what remains future work.
- Use Press when you need outward-facing language that stays inside the published facts.
Why this matters
Adoption gets easier when new readers can answer three questions quickly: what is this, why does it exist next to adjacent protocols, and what can I honestly build against today. This update makes those answers easier to find without inventing a public SDK, issue tracker, or broader governance body that the site has not yet published.