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

AI Memory

Durable Memory and Offline Continuity

Keep typed .uai startup memory useful while authenticated MATM, database, LLM Wiki, AIWikis, or other configured durable systems are available, unavailable, or recovering.

  • Record UAIX-MEMR-4027
  • Path /en-us/ai-memory/multi-agent-workloads/durable-memory/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-MEMR-4027
Surface
AI Memory
Access
Public and linkable

How to use this page

Use this page as part of the current AI Memory 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.

The local .uai/ suite remains hot startup continuity. A configured MATM, LLM Wiki, AIWikis path, database, or other shared memory system is an additive durable layer.

When the runtime is available

  1. Load local .uai/ first for identity, current constraints, ownership, and recovery policy.
  2. Verify the current authenticated runtime contract and authority.
  3. Read back coordinator epoch, leases, per-recipient cursors, idempotency state, and conflicts.
  4. Search or update durable memory only through the configured routes.
  5. Promote reviewed current facts into the project authority layer; do not treat a successful request as proof without readback.

When the runtime or database is unavailable

Continue only inside locally recorded authority. Keep proposed writes queued with stable operation IDs, mark remote delivery, lease, acknowledgement, and durable-memory state unknown, preserve conflicts, and resume from current readback after recovery. The simple local package must remain useful for inspection, bounded work, and handoff even when no API or database is reachable.

Credentials are not memory

Inventory credential file names, locations, intended use, safe hashes, and scope without printing passwords, tokens, keys, cookies, connection secrets, or one-time values. Distinguish deploy authority from API, MATM, database, and tool authority.

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