UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Standards

SPEC-01 Canonical Envelope

UAIX canonical publication-envelope fields, trust posture, validation, redaction, evidence, and execution-boundary rules.

  • Record UAIX-STND-2701
  • Path /en-us/standards/spec-01/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-STND-2701
Surface
Standards
Access
Public and linkable

How to use this page

Use this page for the canonical publication-envelope vocabulary and its mapping to the current UAI-1 transport envelope.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into Conformance Pack, implementation track, changelog, or Project Handoff evidence.

SPEC-01 defines the UAIX canonical publication envelope. It is a portable, evidence-bearing record shape for standards text, handoff payloads, review receipts, public-safe audits, and redaction policies.

Required publication-envelope fields

Field Purpose Current UAI-1 mapping
uaixVersion UAIX standards record version. uai_version
spec Named standard or profile. profile plus registry entry.
envelopeId Stable record identifier. message_id
createdUtc UTC creation time. provenance.issued_at
issuer, issuerDisplayName, issuerPublicUrl Public issuer identity. source and provenance
issuerCapabilityLevel L0-L6 capability context. Capability profile body or extension.
audience Intended reader or receiver. target
lifecycleState Draft, review, accepted, archived, rejected, or superseded state. delivery.lifecycle or body state.
trustPosture Review-only, unsigned, signed-reference, verified, revoked, disabled, unknown, or local-policy-rejected posture. trust plus validator/verifier evidence.
payloadType, payloadSchema, payload Typed body content. body plus registry/schema route.
evidence, redactions Supporting facts and removed sensitive data. provenance, integrity, body evidence, and extensions.
signature, signatureStatus, verification Signature metadata and verifier result. trust plus an explicit verifier record; no implied trust.
exceptions, warnings Review notes and non-blocking issues. Validator issues, conformance result body, or extension records.

Core rules

  • The envelope is portable and evidence-bearing. It is not an execution permit.
  • Receivers must validate shape, inspect evidence, apply local policy, and reject missing authority before acting.
  • Unsigned records can be useful for review, migration, and public examples. They cannot establish trusted identity.
  • Signed records still need verifier output and local trust decisions.

Execution and trust boundary

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

  • UAIX standards records do not authorize execution, tool calls, repository writes, publication, payments, authentication, or durable memory promotion.
  • Local policy, server-side authorization, and human approval override envelope claims.
  • An unsigned envelope can be valid for review, routing, and evidence comparison, but it is not trusted identity.
  • Signed metadata is not trust by itself. A verifier may still report unknown, expired, revoked, disabled, locally untrusted, or otherwise unusable authority.
  • Reference examples for NeuralWikis, LocalEndpoint, Carcinus, MCP, A2A, and custom runtimes are consumer examples only. UAIX.org does not implement their runtime behavior.

Machine-readable companions