Tools

Swarm Readiness

Pre-export and runtime-consumer checklist for workload class, identity, ownership, authority, delivery, coordinator fencing, NPC layering, offline continuity, secrets, and current proof.

  • Record UAIX-TOOL-5560
  • Path /en-us/tools/swarm-readiness/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-TOOL-5560
Surface
Tools
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for Swarm Readiness 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.

Use this checklist before exporting an advanced workload package or claiming a runtime is ready to consume it.

Swarm Readiness
GateRequired evidenceBlocking result
Workload classOne closed class and its exact required surfacesUnknown or independently toggled surface set
IdentityUnique logical IDs and registered namesCollision, missing identity, or runtime instance used as logical identity
OwnershipDisjoint scopes, task owners, acyclic dependencies, integration authorityOverlap, unknown owner, duplicate task, or cycle
AuthorityIntegration, task, shared-state, and applicable migration authorityMissing authority or a request treated as a grant
DeliveryExplicit recipients, per-recipient acknowledgement and cursors, idempotencyGroup acknowledgement, guessed success, or missing readback
CoordinatorLogical coordinator, epoch, lease duration, stale-worker fencingStale epoch or expired/unknown lease
NPC identityPopulation, source persona, logical NPC, runtime, memory, scope, lineage separationIdentity collapse or source mutation
Offline continuityLocal first-load order and unknown-remote-state behaviorPackage becomes unusable or invents success offline
SecretsSafe principal/inventory references onlyPassword, token, key, cookie, connection secret, or one-time credential
ValidationSchema, example, valid fixtures, invalid fixtures, current proofStale proof or skipped blocking fixture

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