process · seven stages, three gates

A ticket cannot skip a stage.

The pipeline is the product. Every change to your store walks the same seven stages in the same order, and three of those stages can send it backwards. Click a stage to see what enters, what leaves, and what stops it.

The seven stages

stage 01 Atlas

Intake

A goal, a complaint or a number that moved becomes a ticket: scope, acceptance criteria, priority and the agents assigned. Atlas writes it, and no downstream agent is allowed to widen it.

enters as
A goal, an anomaly, or a request from you
leaves as
A scoped ticket with acceptance criteria
walkthrough

one real ticket, end to end

  1. Atlas Ticket #4192: mobile ATC buried on PDP. 3 pts, p1. intake
  2. Muse Spec: sticky ATC bar, 3 states, 44px target, safe-area inset. design
  3. Quill Microcopy: "Add — $48" / "Added" / "Sold out". content
  4. Volt Branch sticky-atc pushed. 2 sections, +148 −12. build
  5. Sieve 13 of 14 checks passed. Visual diff on iPhone SE. returned
  6. Volt Fixed overlap with cart drawer at 375px. build
  7. Sieve All 14 checks passed. Visual diff clean. quality
  8. Ledger Metric set: mobile ATC rate, 7-day read, min lift 3%. quality
  9. You Approved at 50% exposure. gate
  10. Relay Deployed behind flag atc_sticky. Watching first hour. ship

the three gates

nothing passes on trust alone
  1. Evidence

    No claim without a spec to back it, no ship without a metric to judge it. Agents that cannot show the evidence do not pass the ticket on.

  2. Peer block

    QA can fail the build agent. SEO can block the copy agent. Data can kill the whole team’s work. No agent can overrule the one that blocked it.

  3. You

    The last gate is a person. Every diff, every reasoning trail, every rollback plan lands with you before it touches a customer.

Watch it happen on a live board.

The Live page shows the same pipeline running on real tickets — queue depth, agent load, and what shipped in the last hour.