Schemas

What the schema set validates

The schema set turns UAI-1 into published validation targets that tools, CI runs, and runtime bridges can apply consistently. The current schema family validates both the shared envelope and the profile-specific body shapes used by the public record.

Current machine-validated envelope

Identity: version, profile, message ID, source, and target.
Workflow state: conversation continuity, delivery mode, expiry, acknowledgement, and optional task references.
Trust posture: channel, auth scheme, principal, optional credential reference, and optional replay-window hints.
Auditability: provenance, integrity, and controlled extension metadata.

Current schema families

uai.intent.request.v1 validates request-side intent, subject, constraints, and response expectations.
uai.intent.response.v1 validates result-side status, request linkage, notices, and optional task handoff.
uai.capability.statement.v1 validates discovery-facing operations, profiles, endpoints, and security schemes.
uai.error.v1 validates typed public failures with status, code, detail, and structured sub-errors.
uai.conformance.result.v1 validates exported validator evidence and artifact references.
uai.task.status.v1 validates async progress, state, result references, and update notes.

What the schemas do not do alone

Schemas are necessary but not sufficient. The validator still applies policy checks such as delivery expiry, trust-reference hints, accepted-response task references, task-status progress consistency, and conformance-summary integrity. The written record still carries semantic intent and support-boundary meaning.

Published schema catalog

Use the catalog below when you need the exact current schema documents that the validator and examples are built against.

[uaix_schema_catalog]

Published field registry

The field registry keeps the keyed JSON source record, the keyless transport order, and the nested body/component order aligned across the public contract. Treat it as part of the machine-readable release record, not as an optional convenience note.

[uaix_field_registry_catalog]

How to use this section

Choose the profile you want to support and resolve its schema.
Check the matching Registry entry and the public field registry before implementing compact transport or body-order assumptions.
Run the Validator with a published Example or candidate message and keep the result with release evidence.
Carry any release-facing change into Implementations, the Changelog, and References and Contributors.

Next step

Continue to Registry for the stable profile map, compatibility cues, and schema-to-example links behind the current release.