Skip to content
Get Started Free

Registry

What the registry provides

The UAIX registry publishes the stable identifiers that make UAI-1 readable by both people and automation. It is the profile map that ties the specification, schemas, fixtures, validator expectations, and support claims together.

What belongs here

  • Profile IDs, record codes, titles, and public status.
  • Schema routes, example routes, and expected validation posture.
  • Compatibility cues that explain which message families are meant to pair together.
  • The release-facing identifiers that other records can cite without guessing.

How the current profiles relate

  • uai.intent.request.v1 usually pairs with uai.intent.response.v1, uai.error.v1, or a later uai.task.status.v1 update.
  • uai.intent.response.v1 stays in the same public envelope and can acknowledge accepted async work through task references.
  • uai.capability.statement.v1 advertises supported operations, profile families, endpoints, and security posture for discovery work.
  • uai.error.v1 is designed to remain legible across request, response, capability, task, and validator flows.
  • uai.conformance.result.v1 records validator evidence for the other published profiles.
  • uai.task.status.v1 keeps async progress public when accepted work cannot be closed in a single response.

Extension and field-order governance

Profile registration and field-order governance should move together. If a release changes keyed-to-keyless order or nested body order, the field registry should change beside the profile record instead of drifting into separate implementation notes.

Current published entries

The registry below ties each public profile identifier to its matching schema, example, and validation posture.

[uaix_registry_catalog]

How to use this section

  1. Resolve the profile before adding support in code or documentation.
  2. Bind that profile to the matching schema, example, and validator expectation.
  3. Use the registry entry as the stable key when attaching release evidence in Implementations, the Changelog, or References and Contributors.

Next step

Continue to Examples to see how the current identifiers, schema rules, and async workflow records appear in working exchanges.