Changelog

How implementers should use this log#

Read the changelog as the public record of what changed, whether the change is additive, corrective, policy-oriented, or breaking, and what migration work a downstream implementation should perform before release.

Release history#

This log records public changes across the UAIX site and standards record so implementers can trace revisions, compatibility expectations, and governance signals without relying on informal notes.

2026-04-25 | Project handoff and AGENTS.md .uai audit hardening#

Change type: Additive developer-handoff and launch-QA clarification.

• Affected records: Project Handoff, AGENTS.md .uai Linking Specification, Reports, Refining UAI Protocol for Agent Communication, Roadmap, launch-surface audits, and canonical workspace docs.
• Migration note: use Project Handoff as the practical draft and first public navigation target for repository context; require the next AI to summarize loaded context, constraints, intended touchpoints, and checks before broad edits; treat Markdown context-profile files and JSON information-profile files as additive draft source formats with explicit loader and trust guardrails.
• Support-claim effect: public pages and launch audits now cover the AGENTS.md/report surfaces, while .uai generators, starter template libraries, upload validators, SDKs, CLIs, and certification remain planned until public evidence exists.
• Reference paths: Project Handoff, AGENTS.md .uai Linking Specification, Refining Report, Roadmap, and Changelog.

2026-04-24 | Launch readiness governance gate release#

Change type: Additive go-live hardening across the public governance and evidence surface.

• Affected records: Launch Readiness, Governance, Policy and Security, Accessibility, API Reference, Conformance Pack, Validator, route inventories, and zh-CN release copy.
• Migration note: use Launch Readiness as the public go-live gate for response checks, package evidence, accessibility QA, locale QA, release-trail alignment, and support-claim boundaries before a broad public push.
• Governance effect: launch hardening now has a named public page that ties existing policy, conformance, validation, discovery, and release-note evidence together without implying a certification or production security program.
• Reference paths: Launch Readiness, Policy and Security, Conformance Pack, Validator, Changelog, and News.

2026-04-24 | Conformance fixture pack release#

Change type: Additive validator-regression and release-evidence expansion.

• Affected records: Adoption Kit, Conformance Pack, API Reference, Roadmap, discovery, production response checks, and the public UAIX REST surface.
• Migration note: release packets can now carry reusable positive keyed/minified-keyed/keyless validator cases, canonical-hash equivalence metadata, and negative checks for missing profile, missing required fields, undeclared fields, invalid traceparent, DID/VC trust evidence, keyless shape, keyless overflow, and unsupported alias.
• Support-claim effect: current validator behavior is easier to regression-test before launch, while alias maps and binary envelopes remain future work until their own fixtures and route behavior exist.
• Reference paths: Adoption Kit, Conformance Pack, Roadmap, Changelog, and News.

2026-04-24 | Implementation evidence checklist release#

Change type: Additive conformance-evidence and developer-handoff expansion.

• Affected records: Adoption Kit, Conformance Pack, API Reference, Roadmap, catalog discovery, and the public UAIX REST surface.
• Migration note: release packets should now carry the implementation evidence checklist beside validator output, fixture references, changelog or release-note links, compatibility notes, and an owner or contact record before support language widens.
• Support-claim effect: the adoption kit and conformance pack now publish a reviewable checklist for moving from first proof to launch evidence without presenting that evidence as certification, badge, or endorsement.
• Reference paths: Adoption Kit, Conformance Pack, Roadmap, Changelog, and News.

2026-04-24 | Validator normalization mode release#

Change type: Additive conformance and compact-transfer hardening.

• Affected records: Validator, API Reference, Conformance Pack, Standards Fit, Roadmap, examples, field registry, OpenAPI, and the public UAIX REST surface.
• Migration note: the validate route now accepts keyed-json, minified-keyed-json, and keyless-json; keyless packets are expanded through the public field registry before schema and policy checks run.
• Support-claim effect: compact keyless transfer now has validator-backed expansion evidence, while alias maps and binary envelopes remain planned or research-track until public fixtures and route behavior exist.
• Reference paths: Validator, API Reference, Conformance Pack, Roadmap, and Changelog.

2026-04-24 | Contact review and standards-fit page release#

Change type: Additive public-operating and specification-boundary expansion.

• Affected records: Contact and Review, Standards Fit, References and Contributors, Governance, Roadmap, launch audits, catalog discovery, and zh-CN localized page bodies.
• Migration note: use the dedicated contact-and-review path for contributor packets and change proposals, and use the standards-fit path when explaining A2A, MCP, OpenAPI, JSON Schema, DID/VC, Trace Context, compact transfer, and normalization boundaries.
• Support-claim effect: public operating and standards-fit guidance is now a page-level launch surface instead of only a roadmap item, while issue trackers, broad governance rosters, alias maps, binary envelopes, SDKs, and certification remain future work until evidence is published.
• Reference paths: Contact and Review, Standards Fit, Roadmap, Changelog, and News.

2026-04-24 | Public roadmap and interoperability route release#

Change type: Additive public-operating-layer and machine-readable guidance expansion.

• Affected records: Roadmap, API Reference, Conformance Pack, the public UAIX REST surface, homepage navigation, and canonical roadmap guidance.
• Migration note: use the published roadmap page and /wp-json/uaix/v1/roadmap as the current forward-plan handoff instead of reconstructing priorities from older research notes.
• Support-claim effect: future-facing interoperability, compact-transfer, normalization, conformance, and developer-handoff ideas now have a public boundary that separates current support, next work, planned work, and research-track ideas.
• Reference paths: Roadmap, API Reference, Conformance Pack, Changelog, and News.

2026-04-23 | UAI-1 specification fit-and-proof update#

Change type: Additive specification-page reframe for launch readers and implementers.

• Affected records: UAI-1, Specification, Schemas, Examples, Validator, API Reference, Adoption Kit, and Conformance Pack.
• Migration note: the UAI-1 page now leads with fit, boundary, proof path, operating surfaces, and launch-support links so readers can move from specification text into current public evidence more quickly. Read the page as the main contract and launch decision surface rather than as a prose-only reference.
• Support-claim effect: implementers can now move from the written contract into schemas, examples, validation, route guidance, and release evidence with less reconstruction work, which reduces the risk of overstating support from partial reading.
• Reference paths: UAI-1, Schemas, Examples, Validator, API Reference, Adoption Kit, Conformance Pack, and the News archive.

2026-04-23 | Adoption kit route and page release#

Change type: Additive onboarding expansion across the public launch surface.

• Affected records: Get Started, Tools, Adoption Kit, API Reference, Conformance Pack, Implementations, and the UAIX core REST surface.
• Migration note: use the published adoption kit page and /wp-json/uaix/v1/adoption-kit as the default first-proof bundle instead of assembling the starter packet manually from scattered routes.
• Support-claim effect: onboarding now has a concrete downloadable handoff bundle before widening support claims.
• Reference paths: Adoption Kit, API Reference, Validator, Conformance Pack, Implementations, and News.

2026-04-23 | Public security-header and trust-hardening release#

Change type: Additive launch hardening across the public response and trust surface.

• Affected records: Policy and Security, API Reference, the public UAIX REST surface, and the UAIX SEO Sweep response layer.
• Migration note: public WordPress-rendered responses now ship with a narrow security-header baseline for framing, referrer handling, browser capability policy, and MIME-type handling. Treat HTTPS redirect, HSTS, and static-file parity as deployment follow-through rather than as already-complete app behavior.
• Support-claim effect: the launch trust posture now has observable response hardening behind it, making it easier to verify the public machine-facing surface without overstating a broader security program.
• Reference paths: Policy and Security, API Reference, Validator, Conformance Pack, Changelog, and News.

2026-04-23 | Dedicated governance policy-page release#

Change type: Additive governance and trust-surface expansion across the launch record.

• Affected records: Governance, Policy and Security, Privacy and Data, Accessibility, Analytics, References and Contributors, About, Press, and related launch guidance.
• Migration note: treat privacy, accessibility, and analytics as published governance child pages rather than as future-tense posture. Use the policy hub plus the dedicated pages when a release changes trust-significant behavior.
• Governance effect: UAIX now publishes a clearer trust-policy section that can be cited directly during launch review without implying a broader institutional program than the site actually maintains.
• Reference paths: Policy and Security, Privacy and Data, Accessibility, Analytics, Changelog, and News.

2026-04-23 | First-proof run and multi-language starter-call release#

Change type: Additive onboarding expansion across the public developer path.

• Affected records: Get Started, Examples, Tools, Validator, API Reference, and the release trail.
• Migration note: the launch surface now publishes a first-proof runbook plus copyable curl, PowerShell, Python, and TypeScript starter requests on the public adoption pages. Use those published snippets and the validator-backed packet as the default onboarding path instead of reverse-engineering the REST surface or inventing a private SDK.
• Support-claim effect: onboarding now points more directly to the current public contract and makes it easier to produce a reviewable first packet without overstating runtime support.
• Reference paths: Get Started, Examples, Validator, API Reference, Conformance Pack, and Implementations.

2026-04-22 | Operating-layer, ownership, and trust-posture clarification#

Change type: Additive public operating-layer clarification across the launch surface.

• Affected records: Governance, Policy and Security, References and Contributors, the shared UAIX Core visual surfaces, and related release-trail language.
• Migration note: use the published operating-layer matrix and handoff packet to explain what is published now, how to verify it, and what is still future work. Keep repository, contributor, ownership, and policy claims scoped to the public record until broader channels are formally published.
• Governance effect: UAIX now makes ownership state, contributor intake, citation and discovery handoff, and trust-significant release posture easier to audit without implying a broader institution than the site currently publishes.
• Reference paths: Governance, Policy and Security, References and Contributors, Implementations, API Reference, Conformance Pack, and News.

2026-04-22 | API reference, conformance pack, and policy surface release#

Change type: Additive launch-support expansion across the public record.

• Affected records: Get Started, Tools, API Reference, Conformance Pack, Governance, Policy and Security, Validator, and the UAIX core REST surface.
• Migration note: machine-facing onboarding now includes a route-level API handbook, a published OpenAPI export, and a reusable conformance packet. Launch-stage trust posture now has a dedicated public page instead of remaining scattered across governance notes.
• Support-claim effect: teams can now point to route documentation, downloadable evidence packets, and a dedicated trust-posture record before widening public support claims.
• Reference paths: API Reference, Conformance Pack, Policy and Security, Validator, Implementations, and News.

2026-04-22 | Developer onramp and protocol-fit clarification#

Change type: Additive public-entry and onboarding clarification across the site.

• Affected records: Home, Get Started, UAI-1, Governance, References and Contributors, and Press.
• Migration note: describe UAI-1 as the public envelope, trust, and evidence layer that can sit above MCP, A2A, and runtime-specific tooling, and use the published pages, machine-readable routes, examples, and validator as the current developer kit.
• Governance effect: UAIX now states more directly what is published today, what is still future work, and how to explain the current single-publisher public record without overstating maturity.
• Reference paths: Home, Get Started, UAI-1, Governance, References and Contributors, Press, and News.

2026-04-22 | Transport, trust, error, and conformance surface release#

Change type: Additive operating-surface release across the public UAI-1 record.

• Affected records: Specification, UAI-1, Tools, Validator, the UAIX core REST surface, capability and conformance examples, and related metadata.
• Migration note: the public record now publishes transport bindings, trust channels, an error registry, and conformance levels. Treat these records as part of the live interoperability and support-claim surface instead of as optional commentary.
• Support-claim effect: teams can now describe transport fit, trust posture, typed failures, and achieved conformance level with more precision when they publish release evidence.
• Reference paths: UAI-1, Tools, Validator, Examples, Implementations, and the News archive.

2026-04-22 | Protocol contract, field registry, and async workflow release#

Change type: Additive and corrective protocol expansion across the public record and machine-readable artifacts.

• Affected records: Specification, UAI-1, Schemas, Registry, Examples, Tools, Validator, the UAIX core REST surface, and related metadata.
• Migration note: the public contract now publishes a richer shared envelope, a field registry for keyed-to-keyless order, typed problem-style errors, validator-backed policy checks, and a dedicated uai.task.status.v1 profile for async workflow visibility. Treat these records as the new current baseline when evaluating compatibility.
• Governance effect: UAIX now states more clearly that UAI-1 is the public exchange and release-record layer that can sit beside orchestration, tool, and trust systems without trying to replace every adjacent protocol.
• Reference paths: UAI-1, Schemas, Registry, Examples, Validator, Implementations, and the News archive.

2026-04-22 | Endpoint and packaged artifact guidance update#

Change type: Additive implementation-surface clarification across the site.

• Affected records: About, References and Contributors, Tools, Validator, Implementations, WordPress Publication Track, and .NET Bridge Track.
• Migration note: use the named route family and packaged artifact list when explaining what UAIX currently publishes, and do not infer a standalone SDK, package registry, or broader runtime catalog unless it is explicitly added to the public record.
• Governance effect: UAIX now makes the current machine-facing endpoints and packaged WordPress artifact family easier to cite, which narrows the credibility gap between the written standards record and the currently shipped implementation surface.
• Reference paths: References and Contributors, Tools, Validator, Implementations, and News.

2026-04-21 | Homepage orientation and trust-surface update#

Change type: Additive public-entry-surface clarification across the site.

• Affected records: Home, the front-page launch surface, and related orientation language.
• Migration note: use the homepage as the short public summary of the current trust posture, published support boundary, and first-read path into the deeper record rather than treating it as a generic brochure lead-in.
• Governance effect: UAIX now makes the front door say more directly what the deeper record already supports, which reduces onboarding ambiguity without widening the published support boundary.
• Reference paths: Home, Get Started, Implementations, Governance, and News.

2026-04-21 | Policy and trust-surface posture update#

Change type: Additive governance and trust-surface clarification across the site.

• Affected records: Governance, References and Contributors, About, Press, and related release-note language.
• Migration note: read privacy, accessibility, and analytics posture as governance-led and release-trail-led on the current launch surface, and do not infer standalone policy programs or broader institutional disclosures that have not yet been published.
• Governance effect: UAIX now states more concretely how policy-significant changes should be described, reviewed, and attached to the public release trail before they are treated as current truth.
• Reference paths: Governance, References and Contributors, About, Press, and News.

2026-04-21 | Release readiness and support-claim guidance update#

Change type: Additive adoption and trust-surface clarification across the site.

• Affected records: Get Started, Implementations, WordPress Publication Track, .NET Bridge Track, Validator, and related release-note language.
• Migration note: distinguish local validation success, release-ready evidence packets, and current public support claims, and keep support language scoped to the published implementation-track record.
• Governance effect: UAIX now states more directly what a passing validator result proves, what additional evidence makes a release reviewable, and when a public support claim becomes justified on the site.
• Reference paths: Get Started, Implementations, WordPress Publication Track, .NET Bridge Track, Validator, and News.

2026-04-21 | Technical record map update#

Change type: Additive technical-orientation clarification across the site.

• Affected records: Specification, UAI-1, Schemas, Registry, Examples, and related release-note language.
• Migration note: use the published profile-family map and compatibility cues when moving from normative reading into schemas, registry resolution, fixtures, and validator-backed evidence, and keep those records aligned rather than treating them as separate references.
• Governance effect: UAIX now makes the current technical stack easier to reconstruct from the public record, which reduces adoption ambiguity without changing validator behavior, routes, or profile support boundaries.
• Reference paths: Specification, UAI-1, Schemas, Registry, Examples, and News.

2026-04-21 | Proof packet and roadmap signal update#

Change type: Additive onboarding and participation-surface clarification across the site.

• Affected records: Get Started, Tools, Governance, References and Contributors, and related release-note language.
• Migration note: use the first public proof run and roadmap-signal guidance when assembling a reusable adoption packet or interpreting current priorities, and treat the published governance and release records as the roadmap until a standalone roadmap or contributor surface is explicitly published.
• Governance effect: UAIX now makes the shortest path from first validation to public participation easier to reconstruct from the published record without implying issue trackers, contact channels, or ecosystem programs that are not yet public.
• Reference paths: Get Started, Tools, Governance, References and Contributors, and News.

2026-04-21 | Evaluation and maturity guidance update#

Change type: Additive public-orientation clarification across the site.

• Affected records: Get Started, About, Press, and related release-note language.
• Migration note: use the published evaluation checklist and maturity framing when assessing current readiness or describing UAIX to third parties, and treat unpublished contact, governance, policy, and runtime surfaces as future work unless they are explicitly published.
• Governance effect: UAIX now distinguishes current public infrastructure from planned growth infrastructure more directly, which makes current readiness easier to cite without overstating institutional completeness.
• Reference paths: Get Started, About, Press, and News.

2026-04-21 | Operating-layer and ownership clarity update#

Change type: Additive public-operating-layer clarification across the site.

• Affected records: Governance, References and Contributors, Implementations, and related release-note language.
• Migration note: treat the current public operating layer as a combination of named attribution, aligned canonical records, validator or implementation evidence, and the release trail rather than as a broader published contact or governance program.
• Governance effect: UAIX now states more concretely where current ownership is published, how release decisions become public truth, and what future implementation tracks must publish before they should be treated as supported.
• Reference paths: Governance, References and Contributors, Implementations, and News.

2026-04-21 | Program model and adoption-kit assembly clarification#

Change type: Additive public-operating-model clarification across the site.

• Affected records: About, Get Started, Implementations, News, and related release-note language.
• Migration note: treat UAIX’s current public work as a record-family and implementation-track surface, not as an events or membership program, and assemble the current adoption kit from the published record until a standalone download is explicitly published.
• Governance effect: UAIX now states more directly how readers should understand the current public operating layer and where adoption packaging already exists today.
• Reference paths: About, Get Started, Implementations, News, and References and Contributors.

2026-04-21 | Implementation scope and release-archive clarification#

Change type: Additive onboarding and release-posture clarification across the site.

• Affected records: Get Started, Implementations, News, and related release-note language.
• Migration note: treat the WordPress Publication Track and .NET Bridge Track as the only current public implementation tracks, use the portable record when evaluating other environments, and read the news archive as a release-note-led public timeline rather than a broader community channel.
• Governance effect: UAIX now states more directly where current public implementation support stops and where future ecosystem work would need new published records before it counts as public support.
• Reference paths: Implementations, News, References and Contributors, and Governance.

2026-04-21 | Conformance packet and regression guidance clarification#

Change type: Additive conformance-evidence clarification across the site.

• Affected records: Implementations, Tools, Validator, Governance, and related release-note language.
• Migration note: keep exported validator results, profile and schema references, fixture baselines, and release links together as a reusable public conformance packet, and do not present that packet as a formal certification badge or endorsement.
• Governance effect: UAIX now states more directly that repeatable conformance evidence and regression-ready fixtures are part of the current trust surface even though a broader formal assurance program remains future work.
• Reference paths: Implementations, Tools, Validator, Governance, and News.

2026-04-21 | Use-case and positioning guidance clarification#

Change type: Additive public orientation and outward-facing language clarification across the site.

• Affected records: About, References and Contributors, Press, and related release-note language.
• Migration note: use the published practical use cases and positioning guardrails when describing UAIX to implementers, researchers, press, and evaluators, and do not imply unpublished partner, contact, or governance structures.
• Governance effect: UAIX now makes the public use-case map and outward-facing limits easier to cite without changing normative behavior or route structure.
• Reference paths: About, References and Contributors, Press, and News.

2026-04-21 | Role paths and public policy posture clarification#

Change type: Additive public orientation and governance clarification across the site.

• Affected records: Get Started, Governance, References and Contributors, and related release-note language.
• Migration note: use the role-based reading paths when onboarding implementers, tool builders, reviewers, and public readers, and treat privacy, accessibility, and analytics pages as planned governance surfaces until they are explicitly published.
• Governance effect: UAIX now states more directly that participation is documentation-led and that policy posture should travel through the same public release trail as the rest of the trust surface.
• Reference paths: Governance, References and Contributors, News, and Implementations.

2026-04-21 | Adoption packet and sitemap surface clarification#

Change type: Additive onboarding and discovery clarification across the site.

• Affected records: Implementations, Tools, the root and locale sitemap surfaces, and related launch-audit coverage.
• Migration note: keep the first-release packet tied to UAI-1, schemas, registry entries, examples, validator evidence, discovery manifests, and sitemap routes, and keep both root and locale-prefixed sitemap surfaces live in release QA.
• Discovery effect: UAIX now states more directly that /sitemap.xml and /sitemap.html are the durable root discovery surfaces while locale-prefixed sitemap routes should continue to resolve the same public inventory for localized readers and tooling.
• Reference paths: Implementations, Tools, References and Contributors, and News.

2026-04-21 | Governance, contributor, and validator workflow clarification#

Change type: Additive public operating-layer clarification across the site.

• Affected records: Governance, References and Contributors, Validator, the machine-readable discovery guidance, and related release-trail language.
• Migration note: use the Validator page for the human-facing workflow, treat the validate REST route as a machine-facing JSON POST endpoint, and use Governance plus References and Contributors as the current public handoff path for contributor and citation context.
• Governance effect: UAIX now states more explicitly that trust infrastructure, public handoff paths, and visible review posture are part of the launch-surface operating layer.
• Reference paths: Governance, References and Contributors, Validator, Implementations, and News.

2026-04-20 | Terminology and implementation-track alignment#

Change type: Corrective public terminology and naming alignment across the site.

• Affected records: homepage copy, Get Started, About, References and Contributors, Implementations, track labels, Press language, and related public release notes.
• Migration note: cite UAIX as the website and publication venue, UAI as the standard family, UAI-1 as the current release, and the WordPress Publication Track and .NET Bridge Track as the current public implementation-track names.
• Governance effect: the public wording now tracks the canonical terminology model more closely, reducing ambiguity without changing routes or validator behavior.
• Reference paths: About, References and Contributors, Implementations, Press, and News.

2026-04-20 | Authority, validator, discovery, and safety rollout#

Change type: Additive standards-positioning update across the public site and runtime.

• Affected records: homepage, About, Specification, UAI-1, Schemas, Examples, Tools, Validator, Governance, Press metadata, the public news archive, and the machine-readable discovery surface.
• Migration note: implementers should align exchanges with published profile declarations, schema checks, provenance fields, integrity metadata, downloadable validation records, and the current discovery manifest before deployment.
• Governance effect: UAIX now states more directly that authority is earned through public review, validator tooling, machine-readable discovery, and auditable implementation evidence.
• Reference paths: About, Specification, UAI-1, Validator, Governance, and News.

2026-04-19 | Public standards site launch#

Change type: Initial public publication release.

• Affected records: primary UAIX route structure, specification pages, governance pages, press resources, implementation packaging, and the public news archive.
• Migration note: use clean locale-prefixed public paths rather than query-string routes when linking or citing public UAIX material.
• Reference paths: Home, UAI-1, WordPress Publication Track, Press, and News.

How this log pairs with other public pages#

• Use News when a changelog entry also needs a public-readable summary.
• Use Implementations when a change affects packaging, runtime evidence, or deployment posture.
• Use References and Contributors when citation, discovery, and attribution links should travel with the release record.
• Use Press when the change also needs approved public language.

What every future entry should capture#

• Release date and affected record family.
• Whether the change is additive, corrective, policy-oriented, or breaking.
• Migration notes for implementations, validators, discovery files, and public references.
• Links back to the canonical documents that were updated.