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

Guides

Swarm Failure and Recovery

Fail-closed recovery from local .uai continuity through runtime contract, epoch, lease, cursor, idempotency, conflict, and current-proof readback.

  • Record UAIX-DOC-4030
  • Path /es-us/guides/swarm-failure-and-recovery/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-4030
Surface
Guides
Access
Public and linkable

How to use this page

Use this page as part of the current Guides public record, then follow its linked standards pages for the next step.

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.

Recovery begins from local startup continuity and proves current runtime state before remote work resumes.

Failure states

Record service unavailable, service unreachable, unauthorized, stale coordinator epoch, expired process lease, unknown delivery, lost response, cursor gap, and revision conflict as distinct states.

Recovery order

  1. Load .uai/startup-packet.uai, then the swarm root, roster, allocation, shared-state policy, recovery policy, and current receiver brief.
  2. Verify the current runtime contract and authentication boundary.
  3. Read back coordinator epoch and process lease.
  4. Resume from each recipient cursor.
  5. Reconcile stable idempotency keys after lost responses.
  6. Preserve stale-parent and concurrent conflicts.
  7. Record current canonical proof before claiming delivery, acknowledgement, completion, durable write, or lease ownership.

Fail-closed behavior

If identity, authority, parent revision, lease, delivery state, or credential scope is unknown, stop the affected remote operation and request review. Local inspection and other independently authorized work may continue.

Support boundary

Agent runtimes execute. UAIX records portable configuration, logical identity, authority boundaries, routing references, reviewed evidence, and offline continuity. Runtime systems retain authentication, credential verification, leases, queues, transactions, tool execution, database writes, and delivery readback. A missing-authority request is review-pending only and applies no grants.

Schemas and validation