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

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

  • Record UAIX-STND-2254
  • 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-2254
Surface
Standards
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for SPEC-02 Project Handoff 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-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