Skip to content
Get Started Free

UAI-1 Standards Overview

UAI-1 is the current UAIX exchange contract. It publishes a reviewable envelope, profile registry, field registry, schemas, examples, validator behavior, release records, and safety boundaries for AI-system communication.

Current envelope owner

The current UAI-1 transport envelope remains the published snake_case record used by schemas, examples, registry records, field-order normalization, and validator evidence: uai_version, profile, message_id, source, target, conversation, delivery, trust, body, provenance, integrity, and extensions.

Publication vocabulary

SPEC-01 adds a canonical publication-envelope vocabulary for standards text and handoff records. It maps to the transport envelope instead of replacing it, so existing validator fixtures and keyless field-order records remain stable.

Normative companions

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