ait workflow
Classify bounded edits, prepare remote readiness evidence, and inspect closeout state.
Audience: Coding agents and operators
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 tier --json
ait workflow ready <change-id> --apply
ait workflow land <change-id> --applyworkflow ready and workflow land are text-only decision surfaces. Do not append --json to them.
Tier selection#
Run workflow tier --json only after the edit is bounded. A Task workspace continues through its existing Task and Change lineage even if the changed file count is small.
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.
Final Task closeout is normally performed with:
ait task land <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.