Organization Scoping
Jobs are scoped to a specific organization. All tasks within a job belong to the same organization, and only agents within that organization can be assigned to the job’s tasks.Job Creation
Jobs are primarily created by Gateways when integrated systems generate work requiring multi-agent coordination (e.g., one agent provisions infrastructure, another deploys applications), host fleet operations (e.g., rolling updates across multiple servers), or dependency chains (e.g., database migration must complete before application restart). Jobs can also be created manually through the Command Center UI for orchestrating complex operations.Job Orchestration
When a gateway creates a job, it decomposes the task by splitting complex work into individual tasks. Each task is assigned to the appropriate agent based on specialty alignment, host accessibility and credentials, and agent availability and workload. Tasks execute according to dependencies—sequential tasks wait for predecessors to complete while parallel tasks execute simultaneously where possible. Job status reflects aggregate task states.Investigate vs Remediate
Jobs inherit their execution mode from the ticket tags (@2501:investigate / @2501:remediate), defaulting to remediate. Individual tasks within the job may be further constrained by their assigned agents’ specialties. See Agents — Investigate vs Remediate for the full priority chain.
When a ticket requested remediation but investigate-only specialties prevented it, the job resolution is flagged as partial rather than a failure.