A durable swarm needs stable logical identity, explicit fan-out, independent recipient state, coordinator fencing, and conflict-preserving writes. Portable UAIX records describe those contracts; the selected runtime implements and proves them.
Identity and delivery
- Logical agent ID survives process restart; runtime instance and process lease do not.
- One material message expands into explicit recipient deliveries. Delivery, read, acknowledgement, work acceptance, and completion are distinct states per recipient.
- Each recipient advances its own cursor. One recipient cannot acknowledge or advance another recipient.
- Retries use one stable idempotency key, and a lost response is resolved by readback rather than by inventing success.
Coordinator and conflict rules
- Coordinator identity and epoch are explicit.
- Workers reject stale epochs and expired process leases.
- Shared writes use exact-parent or compare-before-replace semantics when the runtime supports them.
- Concurrent or stale-parent writes remain typed conflicts for review; they are not silently overwritten.
Capability discovery
Before remote work, verify the current runtime contract, exact supported operations, schema identity, authentication boundary, delivery/readback behavior, and unavailable-operation response. Discovery does not grant authority.
Open the Agent Swarm setup mode.
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