UAIX has tightened the public onboarding and discovery surface so implementers can assemble a first-release packet and verify both root and locale sitemap routes during launch QA.
What changed
- Implementations now defines a starter adoption packet that keeps UAI-1, schemas, registry entries, examples, validator evidence, discovery links, and release notes together.
- Tools now states more directly how the root discovery files and the locale-prefixed sitemap routes should be used during automation and public QA.
- The launch audit now checks
/sitemap.xml,/sitemap.html,/en-us/sitemap.xml, and/en-us/sitemap.htmlso sitemap availability stays part of release evidence.
How implementers should use this
- Start with UAI-1 and the current supporting records.
- Carry validator evidence and discovery links through the relevant Implementation track.
- Use References and Contributors, the Changelog, and News as the public handoff and release trail around the packet.
Why this matters
UAIX is strongest when the public record is easy to discover, easy to validate, and easy to ship against. This update makes the adoption layer more operational by keeping discovery and evidence attached to the same release path.