← All screensSIDEBAR · EXECUTIONPipeline with agent fleet, ticket controls, ordered stages, artifact review and run log.
Why it exists
Safe operating sequence
Select agent → enter ticket → dry run → inspect paths, artifacts and stages → human decision → prepare sealed publication → approve finalization.
Control
Meaning
Run pipeline
Fetches ticket context and creates an independent job for the selected agent.
Commit, push & update Jira
Requests outward finalization; leave off for a dry test. Publication still requires its governed approval.
Processes / Stop
Shows active and queued jobs, switches to their exact workflow, and requests cooperative cancellation.
Accept / Ignore / Open review
Completes dry-run human sign-off. Accept teaches Fabric; Ignore is neutral.
Continue / Prepare publication
Turns an approved dry run into a separate sealed publication approval for its exact artifacts.
Activity log / Synced files
Explains stage events and exact Perforce outputs.
Batch rule: each ticket owns its job, artifact manifest and outcome. A failed job must not prevent an independent job from running or contribute files to its publication.