issue-pipeline.yml — labels as state

issue-pipeline.yml — labels as state A lifecycle diagram generated by Archify. 01 / Pipeline stages (labels) 02 / Human gates + Blocked + retry 03 / Terminal agent:queued · scan picked it up · Pipeline stages (labels) · deterministic 01 agent:queued scan picked it up deterministic T1 intake · evidence + template · Pipeline stages (labels) · isolated env 02 T1 intake evidence + template isolated env agent:ready · autonomy gates pass · Pipeline stages (labels) · gate 03 agent:ready autonomy gates pass gate agent:in-pr · T2 implement → draft PR · Pipeline stages (labels) · FLEET_TOKEN 04 agent:in-pr T2 implement → draft PR FLEET_TOKEN agent:done · T3 made it mergeable · Pipeline stages (labels) · ready for review 05 agent:done T3 made it mergeable ready for review agent:hold · human paused it · Human gates · brake agent:hold human paused it brake human-review · T3 stops before ready · Human gates · brake human-review T3 stops before ready brake agent:blocked · evidence or gate failed · Blocked + retry · retryable agent:blocked evidence or gate failed retryable Merged by a human · never by a tier · Terminal · terminal Merged by a human never by a tier terminal Legend start active state waiting decision terminal success failure / exit external

Stage is a label

  • • scan derives the stage from labels — no event chain to lose
  • • Per-tier caps and autonomy gates live in fleet.yml
  • • Evidence comes from a real clone and toolchain

Human brakes

  • • agent:hold stops any issue with one label edit
  • • human-review keeps the PR a draft until a person looks
  • • security types and size:xl are assisted, never autonomous

Blocked is not failed

  • • agent:blocked is retryable once a human unblocks
  • • CI-bearing PRs use FLEET_TOKEN, never GITHUB_TOKEN
  • • Every path ends in a human merge