Automation

Repeatable work needs an execution record

E4S background workers, leases, retries, notifications, and audit events support bounded infrastructure workflows. Fleet Runner lets a permitted operator select registered targets and submit an approved operation; the resulting per-target outcome matters more than a single “started” message.

Before dispatch

1. Confirm that the active workspace owns every selected target.
2. Review the operation and expected effect.
3. Check that the necessary agent capability is available.
4. Choose a suitable window and an operator who can review the result.

Cancellation may stop work that has not started, but it cannot undo a command already executed. Avoid including secrets in command text or public evidence. Read the Fleet Runner guidance before running work across multiple assets.