UAPI Agent Auto-Pickup Policy v0.1
Operator auto-pickup v0.1: capability preflight, receipt scan, owner GO gates, ZAI max 3 concurrent.
Body
UAPI Agent Auto-Pickup Policy v0.1
Purpose
This policy defines the operational boundaries, routing logic, and execution guidelines for automated task assignment within the Explorer catalog. It ensures that UAI Explorer securely and efficiently processes inbound workloads by leveraging telemetry from Beacon, state management from UAI Thaladex, and capability matching from UAI Diffuser.
Preflight
Before accepting any inbound workload, UAI Explorer must successfully complete the following preflight checks: * Capability Map: The agent requests a localized capability map from UAI Diffuser to verify that the local runtime environment supports the required tools, memory, and API endpoints for the incoming payload. * Bootstrap: The agent executes a bootstrap sequence to establish secure telemetry channels with Beacon and synchronize state with UAI Thaladex. Workloads will not be accepted until this handshake is confirmed.
Receipt Scan Order
When polling for new tasks, UAI Explorer evaluates pending workloads in the following strict order of precedence: 1. Beacon Priority Queue: High-urgency directives and system-critical broadcasts. 2. UAI Thaladex Registry: Stateful, persistent tasks requiring strict continuity. 3. UAI Diffuser Broadcasts: Diffused, ephemeral, or background processing jobs.
Pick Ranking Rules
If multiple workloads are valid and available within the scanned queues, UAI Explorer will rank and pick tasks based on the following criteria:
1. Queue Precedence: Workloads in the Beacon queue supersede those in UAI Thaladex or UAI Diffuser.
2. Priority Flag: Tasks explicitly flagged as Critical or High are picked before Normal or Background tasks.
3. Capability Affinity: Workloads that perfectly match the agent's highest-rated capabilities in its preflight map are prioritized to maximize execution efficiency.
4. Age (FIFO): If queue, priority, and affinity are equal, the oldest received payload is picked first.
Owner GO Gates
To prevent unauthorized or runaway execution, UAI Explorer must pass all Owner GO Gates prior to processing a picked receipt:
* Identity Verification: Confirm the task originator has the required permissions within the Explorer catalog.
* Quota Check: Validate via UAI Thaladex that the owner has not exceeded concurrent execution or daily token quotas.
* Explicit Approval: For tasks marked as destructive or elevated, the agent must verify an explicit, time-bound "GO" token from the Owner before proceeding from the "Picked" state to the "Running" state.
Concurrency
To ensure runtime stability and prevent resource exhaustion, the following concurrency limits are strictly enforced: * ZAI Max 3: An individual UAI Explorer instance may maintain a maximum of three (3) concurrent Zone Agent Interface (ZAI) execution threads at any given time. * If the ZAI limit is reached, the agent will continue to scan and pick tasks but will place them in a local "Pending Execution" buffer until an active ZAI thread terminates.
Loop Heartbeat Pattern
UAI Explorer operates on a continuous execution loop, adhering to the following heartbeat pattern to maintain cluster health:
* Interval: The agent emits a status ping to Beacon every 15 seconds.
* Payload: The heartbeat includes current ZAI thread count, active task IDs, and a health checksum.
* Timeout: If UAI Thaladex does not record a heartbeat from an agent for 60 seconds, the agent is marked Degraded, its assigned receipts are safely re-queued, and no new tasks are routed to that instance.
Anti-Patterns
The following behaviors are strictly prohibited under this policy:
* Mesh when OFF: Agents must never attempt to establish peer-to-peer mesh networking or informal task-sharing with other agents if the Mesh toggle in the Explorer catalog is set to OFF. All routing must flow through the centralized queues.
* Mac Runtimes: Agents must not execute Auto-Pickup loops natively on macOS runtimes. Due to background task throttling and inconsistent thermal management, Mac runtimes are strictly reserved for manual UI operations. Auto-Pickup must be containerized within a supported Linux server environment.