UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIXUniversal Artificial Intelligence ExchangePublic standards publication
CurrentUAI-1 v1.0
  • Current versionUAI-1 v1.0
  • Plain-English definitionOpen message format for auditable AI-to-AI exchange
  • Current attributionMichael Kappel and the UAIX contributors
  • Start hereGet 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-2253
  • 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-2253
Surface
Standards
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for SPEC-01 Canonical Envelope and its standards-facing content.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

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

Required publication-envelope fields
FieldPurposeCurrent UAI-1 mapping
uaixVersionUAIX standards record version.uai_version
specNamed standard or profile.profile plus registry entry.
envelopeIdStable record identifier.message_id
createdUtcUTC creation time.provenance.issued_at
issuer, issuerDisplayName, issuerPublicUrlPublic issuer identity.source and provenance
issuerCapabilityLevelL0-L6 capability context.Capability profile body or extension.
audienceIntended reader or receiver.target
lifecycleStateDraft, review, accepted, archived, rejected, or superseded state.delivery.lifecycle or body state.
trustPostureReview-only, unsigned, signed-reference, verified, revoked, disabled, unknown, or local-policy-rejected posture.trust plus validator/verifier evidence.
payloadType, payloadSchema, payloadTyped body content.body plus registry/schema route.
evidence, redactionsSupporting facts and removed sensitive data.provenance, integrity, body evidence, and extensions.
signature, signatureStatus, verificationSignature metadata and verifier result.trust plus an explicit verifier record; no implied trust.
exceptions, warningsReview 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