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-02 Project Handoff

Portable project memory and custody transfer contract for humans, agents, vendors, and future sessions.

  • Record UAIX-STND-2702
  • Path /en-us/standards/spec-02-project-handoff/
  • Use Canonical public record

Document status

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

How to use this page

Use this page for the Project Handoff custody-transfer contract and portable memory record fields.

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-02 defines Project Handoff as portable project memory and custody transfer. It tells a receiving human or agent what to read, what is current, which constraints apply, what work is next, and which checks protect the handoff.

Required custody fields

  • projectId, handoffId, createdUtc, owner, and custodian.
  • frontDoor, memoryRoots, requiredReads, and doNotLoadByDefault.
  • currentState, constraints, decisions, nextActions, risks, and targetedChecks.
  • evidence, redactions, warnings, exceptions, and localPolicyWins.

Reference-only scenarios

  • NeuralWikis memory handoff: a reviewed memory packet may point to wiki-derived evidence without giving a runtime permission to publish or mutate production content.
  • LocalEndpoint safe local capability: a local runtime may consume the packet as input, but the local endpoint owns execution controls, file access, and consent gates.
  • Carcinus public profile handoff: a public orchestrator profile can receive evidence records while Carcinus remains the runtime owner outside UAIX.org.

Current public page

The practical adoption page remains Project Handoff. This SPEC-02 page names the tighter record contract and points to the matching schema/example profiles.

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