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-4023
  • 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-4023
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.

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

Class Required surfaces Use when
Multiple agents in one codebase Shared codebase, durable messaging Two or more agents work concurrently under explicit scopes and one integration authority.
Distributed agent swarm Durable messaging, durable memory, external tool execution Workers restart, messages fan out, per-recipient delivery matters, and current runtime state requires readback.
Database-backed NPC population Durable memory, database persona projection, shared world state, external tool execution Large NPC populations need stable identity, scoped runtime assembly, revision lineage, and separately retained learned memory.
Hybrid multi-agent system All advanced surfaces, including release and schema change One 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

Feature Human routes Machine and generated renderers
Workload selection Overview, Wizard Guide, wizard setup fragments Wizard payload, manifest overlay, schema, registry, example
Code ownership Same-Codebase Agents, Code Ownership guide Roster, work allocation, root manifest, per-agent receiver brief
Swarm delivery Swarm Compatibility, Failure and Recovery Coordinator/delivery block, communication records, conformance fixtures
NPC identity Database-Backed NPCs NPC identity block, persona storage binding, schema and fixtures
Offline continuity Durable Memory, Failure and Recovery Startup 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