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

AI Memory

Advanced Multi-Agent Workloads

Additive guidance for simultaneous code agents, durable distributed swarms, database-backed NPC populations, hybrid systems, and useful offline .uai continuity.

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

Document status

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

How to use this page

Use this page as the canonical public reference for Advanced Multi-Agent Workloads 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.

Start with the Base wizard mode and local typed .uai/ files for one human working with one agent. Select an advanced workload only when simultaneous code ownership, durable distributed coordination, a database-backed NPC population, or a hybrid system creates real additional requirements.

Closed workload classes

Closed workload classes
ClassRequired surfacesUse when
Multiple agents in one codebaseShared codebase, durable messagingTwo or more agents work concurrently under explicit scopes and one integration authority.
Distributed agent swarmDurable messaging, durable memory, external tool executionWorkers restart, messages fan out, per-recipient delivery matters, and current runtime state requires readback.
Database-backed NPC populationDurable memory, database persona projection, shared world state, external tool executionLarge NPC populations need stable identity, scoped runtime assembly, revision lineage, and separately retained learned memory.
Hybrid multi-agent systemAll advanced surfaces, including release and schema changeOne workload combines code, durable coordination, NPC/database state, tools, deployment, and migrations.

Source-of-truth order

  1. Workspace manifest or workspace.uai.
  2. Active typed .uai/ memory.
  3. Project docs and runbooks.
  4. Machine-readable manifests.
  5. Referenced or adjacent credential inventory files, using safe metadata only.
  6. Current live proof reports.
  7. Current web, API, or database state.

Do not stop after environment variables or a tool list when workspace guidance says credentials or authority references may be local files.

Route-to-renderer coverage

Route-to-renderer coverage
FeatureHuman routesMachine and generated renderers
Workload selectionOverview, Wizard Guide, wizard setup fragmentsWizard payload, manifest overlay, schema, registry, example
Code ownershipSame-Codebase Agents, Code Ownership guideRoster, work allocation, root manifest, per-agent receiver brief
Swarm deliverySwarm Compatibility, Failure and RecoveryCoordinator/delivery block, communication records, conformance fixtures
NPC identityDatabase-Backed NPCsNPC identity block, persona storage binding, schema and fixtures
Offline continuityDurable Memory, Failure and RecoveryStartup packet, swarm recovery, generated overlay

A feature is incomplete when an equivalent route, generated file, schema, example, registry record, or validator path remains stale.

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

Architecture proposals

UAI-1 v1.0 remains the current published contract. Explore separately versioned proposals for independent exchange, capabilities, recovery and source preservation.

Proposed designs and local reference examples; hosted runtime services and independent interoperability are not claimed.

The English proposal is the source for normative interpretation.

Read the architecture proposals · Machine-readable proposal catalog