UAIX has expanded the launch-facing support surface so implementers can move from the written standard into machine-facing integration and launch-trust review without reverse-engineering the site.
What changed
- API Reference now publishes the live route inventory, starter requests, and OpenAPI export for the current UAIX REST surface.
- Conformance Pack now assembles the current public schemas, registry records, fixtures, operating guidance, and launch pointers into one reusable JSON packet.
- Policy and Security now states the current launch-stage posture for licensing, privacy, accessibility, analytics, and security-sensitive release discipline.
- The machine-facing
/wp-json/uaix/v1/openapi.jsonand/wp-json/uaix/v1/conformance-packroutes now give automation the same launch packet that the public pages explain.
How to use this update
- Start with API Reference when you need the exact REST contract, non-locale base path, and starter calls.
- Use Conformance Pack when validator evidence, record inventory, and launch pointers need to travel together as reusable review material.
- Use Policy and Security with Governance when a launch review depends on the current trust posture rather than only on route behavior.
- Keep the Changelog, News, and Implementations attached when these surfaces support a public release or support claim.
Why this matters
UAIX becomes easier to adopt when a new implementer can see the machine-facing contract, reusable evidence packet, and launch-stage trust posture as one connected support surface instead of scattered hints. This update moves the site closer to that bar while staying honest about what is and is not yet institutionalized.