UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIXUniversal Artificial Intelligence ExchangePublic standards publication
CurrentUAI-1 v1.0
  • Current versionUAI-1 v1.0
  • Plain-English definitionOpen message format for auditable AI-to-AI exchange
  • Current attributionMichael Kappel and the UAIX contributors
  • Start hereGet Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Publication record

UAIX-NEWS-0024

UAIX Protocol Contract and Field Registry Release

UAIX expanded UAI-1 into a richer public exchange contract with a field registry, async task-status coverage, and stronger validator-backed protocol guidance.

Published
Updated

UAIX has moved UAI-1 from a thinner message format into a more operational public exchange contract with a richer shared envelope, a published field registry, better async workflow coverage, and stronger validator-backed evidence.

What changed

  • UAI-1 now explains the current common envelope more directly, including conversation state, delivery semantics, trust metadata, provenance, integrity, and extensions.
  • Schemas, Registry, and Examples now publish six current profiles, including uai.task.status.v1 for async work and stronger typed error handling.
  • The public field registry now keeps keyed JSON, keyless transport order, and nested body order aligned across the current release.
  • Tools and the Validator now describe the route family and policy checks more clearly so the public record is easier to automate against.

How to use this update

  1. Start on UAI-1 for the new envelope and boundary description.
  2. Use Schemas, Registry, Examples, and the field registry together when evaluating compatibility.
  3. Use the Validator to turn that updated contract into reviewable conformance evidence.
  4. Carry any release-facing support claim through Implementations and the Changelog so the broader public record stays aligned.

Why this matters

UAIX becomes more credible when the standard explains real workflow state, trust hints, field order, and conformance evidence on the public record instead of leaving those details as future work or local convention. This update is a substantial step toward making UAI-1 a practical public coordination layer for AI-to-AI systems.

Release context

Read this update as one record inside a wider release trail

This dated post is useful on its own, but launch review depends on the build record, changed routes, validation links, and public evidence surfaces that travel with it.

Public records touched

  • UAI-1 UAIX-SPEC-0048

    Current normative release for UAI, including the shared envelope, transport/trust/error/conformance operating surfaces, the async task-status profile, validation expectations, and implementation reading order.

  • Schemas UAIX-SCHE-0053

    Published UAI-1 schemas, field-order governance, validator policy checks, and the line between machine rules and the written specification.

  • Registry UAIX-REGI-0054

    Published UAI-1 profile IDs, schema links, example links, compatibility notes, and the profile map behind the current release.

  • Examples UAIX-EXAM-0055

    Example UAI-1 request, response, capability, error, conformance, and task-status records that connect the specification, schemas, registry, and validator.

  • Tools UAIX-TOOL-0059

    Validator, discovery, field-registry, and review tools that help teams test and adopt UAI-1.

  • Validator UAIX-TOOL-0060

    Validate UAI-1 messages against published profiles, field-order rules, and policy checks, then export reviewable results before release.