{"standard_family":"UAI","current_release":"UAI-1","uai_version":"1.0","release_date":"2026-06-10","description":"Published trust-channel guidance for the values allowed in `trust.channel`, trust metadata tail fields not required for compact trust readers, and the minimum controls expected before public compatibility claims are made.","channels":[{"id":"public-web","title":"Public Web","summary":"Publicly readable records over HTTPS with no prior bilateral trust setup.","minimum_controls":["HTTPS","Stable public URI","Integrity checksum"],"recommended_controls":["signature_ref","ETag or cache validation on published artifacts"],"fit":"Discovery, schemas, registry, examples, and conformance evidence."},{"id":"private-api","title":"Private API","summary":"Service-to-service exchange on a scoped network or tenant boundary.","minimum_controls":["HTTPS","Authorization policy","Replay-aware message handling"],"recommended_controls":["traceparent","credential_ref or audit-log linkage"],"fit":"Partner integrations and private deployment surfaces."},{"id":"mtls","title":"Mutual TLS","summary":"Transport-authenticated exchange where peer identity is anchored at the connection layer.","minimum_controls":["Mutual TLS","Certificate lifecycle management","message_id replay handling"],"recommended_controls":["signature_ref for durable public evidence","traceparent"],"fit":"High-assurance service boundaries."},{"id":"signed-envelope","title":"Signed Envelope","summary":"Message-level signature or detached signature reference accompanies the record.","minimum_controls":["signature_ref","Integrity checksum","Replay-window handling"],"recommended_controls":["credential_ref","Public verification material"],"fit":"Records that must remain verifiable after transport or storage boundaries change."},{"id":"credentialed","title":"Credentialed","summary":"The sender or execution context is backed by a machine-verifiable credential or comparable signed identity assertion.","minimum_controls":["credential_ref","Identity-to-principal mapping","Replay-window handling"],"recommended_controls":["signature_ref","Public trust-root documentation"],"fit":"Inter-organization exchange where portable trust evidence matters."}],"identity_shapes":[{"id":"uri","fit":"Use when a stable HTTPS origin is enough to identify the participating system."},{"id":"did","fit":"Use when a portable principal identifier or verifier ecosystem is needed."},{"id":"service-scoped-id","fit":"Use when authority stays inside one provider boundary but still needs a durable principal string."}],"metadata_fields":[{"id":"trust_profile","type":"string","required":false,"guidance":"Names the profile or local policy used to interpret the trust metadata. It is descriptive and does not make one credential stack mandatory."},{"id":"verification_status","type":"enum","required":false,"guidance":"Records the verifier posture when a verifier was consulted or deliberately not consulted."},{"id":"credential_status","type":"enum","required":false,"guidance":"Records the credential-reference posture without storing raw credentials or implying UAIX.org validated the credential."},{"id":"verifier_ref","type":"uri","required":false,"guidance":"References the verifier, verifier policy, or review record used by the publisher or receiving environment."},{"id":"trust_root_ref","type":"uri","required":false,"guidance":"References the trust-root document or authority material the publisher expects consumers to review."},{"id":"proof_ref","type":"uri","required":false,"guidance":"References detached proof, signature, or verification evidence. Do not place raw tokens, private keys, or credential secrets here."},{"id":"replay_policy_ref","type":"uri","required":false,"guidance":"References the replay-window or acceptance policy associated with `trust.replay_window_id`."},{"id":"verification_checked_at","type":"utc-date-time","required":false,"guidance":"Records when the verification posture was checked or recorded."},{"id":"verification_expires_at","type":"utc-date-time","required":false,"guidance":"Records when the verification or replay posture should be considered stale."},{"id":"assurance_level","type":"enum","required":false,"guidance":"Summarizes assurance as a local-policy descriptor, not a UAIX certification or endorsement."}],"verification_status_values":["not_verified","verified","failed","expired","revoked","unknown"],"credential_status_values":["not_checked","valid","invalid","expired","revoked","unknown"],"assurance_level_values":["self_asserted","reference_only","transport_authenticated","signed_reference","credential_verified","local_policy_verified"],"operational_controls":[{"id":"replay-window","guidance":"Use `trust.replay_window_id` to bind message acceptance to a replay policy instead of treating signatures as replay protection by themselves."},{"id":"public-evidence","guidance":"When a support claim becomes public, keep signature, credential, or verifier references attached to the same release packet as the validated message."},{"id":"least-disclosure","guidance":"Expose only the identity and credential material needed to justify the public exchange claim; do not leak private trust metadata by default."},{"id":"verifier-reference","guidance":"Use `trust.verifier_ref` to cite the verifier or policy record instead of embedding verifier output or private reviewer notes in the packet."},{"id":"proof-reference","guidance":"Use `trust.proof_ref` for detached proof material and keep raw secrets, bearer tokens, private keys, and credential payloads out of UAI records."},{"id":"trust-root-reference","guidance":"Use `trust.trust_root_ref` when a consumer needs to know which trust-root material was intended for review."},{"id":"verification-expiry","guidance":"Use `trust.verification_expires_at` when a verification or replay posture should be treated as stale after a known UTC instant."},{"id":"replay-policy-reference","guidance":"Use `trust.replay_policy_ref` to explain replay-window semantics without treating signatures as replay protection by themselves."}],"support_boundary":"Trust metadata is descriptive evidence and verifier-reference material. UAIX.org does not perform hosted credential validation, issue certification, endorse implementations, provide runtime enforcement, or make any credential stack mandatory.","adjacent_standards":[{"name":"Model Context Protocol Authorization","url":"https:\/\/modelcontextprotocol.io\/specification\/2025-11-25\/basic\/authorization","fit":"When UAI rides beside MCP-style sessions, follow audience-bound OAuth patterns instead of tunneling bearer semantics through UAI fields."},{"name":"W3C Verifiable Credentials Data Model","url":"https:\/\/www.w3.org\/TR\/vc-data-model\/","fit":"Use VC-style credentials behind `credential_ref` when portable machine-verifiable identity matters."},{"name":"A2A Signed Agent Cards","url":"https:\/\/a2a-protocol.org\/latest\/announcing-1.0\/","fit":"Use signed capability metadata for discovery; UAI-1 can carry equivalent trust material inside the message record and release evidence."}],"route_url":"https:\/\/uaix.org\/wp-json\/uaix\/v1\/trust-channels"}