Fleet readiness

Place work only after the host, task, and transport each present current evidence. Keeping those dimensions explicit gives dispatchers a dependable go/no-go result and makes the owning prerequisite clear whenever placement pauses.

What it adds

Fleet readiness synthesizes that placement decision. It checks configuration, projects, agent surface, inventory, authentication, and transport prerequisites for the selected machine and work unit.

How it works

Readiness stays separate for execution host and target platform. The result is ready, blocked, or unknown with evidence for each required row; the dispatcher consumes the complete result before placement.

> Prove whether host-a can run this delivery and show host, task, and transport separately.
host=ready evidence=inventory+projects+agents
task=ready evidence=scope+capabilities
transport=ready evidence=ssh+identity
execution_host=host-a target_platform=linux
result=ready

Scope

Fleet readiness synthesizes prerequisite evidence. Inventory, agent parity, project checks, auth, and remote administration own their detailed mechanics.

Source

Ships in the roundhouse plugin.

Proof point

host=host-a state=ready
task=delivery-opaque-01 state=ready
transport=ssh state=ready
placement=allowed