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
- Workspace manifest or
workspace.uai. - Active typed
.uai/memory. - Project docs and runbooks.
- Machine-readable manifests.
- Referenced or adjacent credential inventory files, using safe metadata only.
- Current live proof reports.
- 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
- Advanced Multi-Agent Workload schema
- Reference workload example
- UAI-1 profile registry
- Swarm Readiness checklist