Fleet Ops / RapidRFQ
Running Clean Warn Error Critical Idle / gated

After station 8

  1. The resolver applies only repairs that carry their own detector, then re-runs that detector. A fix it cannot verify is never proposed.
  2. It commits to a branch and opens a pull request — never to main, because main auto-deploys to reps, so an agent with main is an agent that ships to customers.
  3. You merge. That is the approval step, and it sits deliberately outside this diagram: no agent can perform it.

Tickets with no verified recipe get a comment explaining the diagnosis instead of a patch. A confident wrong fix costs more to review than an open ticket.

What's breaking 0

Gates 0