ait workflow

Role#

Normally run by the coding agent. Operators may use the same decision surfaces to inspect a remote gate without bypassing it.

Purpose#

ait workflow classifies bounded edits, prepares remote Patchset readiness, and inspects or resumes closeout. Effective scope and exact commands come from the generated repository instructions.

Syntax#

ait workflow guide [topic]
ait workflow reconcile --dry-run --json
ait workflow ready <change-id> --apply
ait workflow finish <change-id> --apply

workflow ready and workflow finish are text-only decision surfaces. Do not append --json to them.

Guide and reconciliation#

workflow guide prints one supported playbook. workflow reconcile inventories cross-object Task, Change, Line, worktree, Land, and Plan-binding state. Its default and explicit --dry-run forms do not mutate Plan state; use --apply only for a reviewed reconciliation action.

Remote readiness#

workflow ready --apply can create or synchronize the selected Patchset and advance required CI, attestation, review, and policy state. It stops with one exact next action when a gate needs separate work.

The explicit remote reviewer-owned closeout is:

ait workflow finish <change-id> --apply

It checks the selected Patchset's review and policy requirements before the safe atomic finish. Configured local closeout, or remote closeout after all readiness evidence is already complete, can instead use:

ait task finish <task-or-change-id>

Failure and recovery#

Do not substitute local checks for required remote CI, append unsupported output flags, or switch authority to avoid a blocker. Re-run the decision surface after the owning evidence changes and preserve the same Change ID.

Related#

• ait task
• ait queue
• Remote Infrastructure