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 01Atlas
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
stage 02Muse
Design
Layout, states and spacing against your existing design language. The output is a spec with redlines and every interaction state — not a picture for the build agent to interpret.
enters as
A scoped ticket
leaves as
A layout spec with all states redlined
stage 03Quill + Beacon
Content
Copy in your voice, checked against product specs, with metadata and structure reviewed for anything that would cost organic traffic. Two agents work the same ticket and can block each other.
enters as
A layout spec with copy slots
leaves as
Copy, microcopy, metadata and schema
stage 04Volt + Forge
Build
The spec becomes theme code and API work on a branch. Accessibility, breakpoints and interaction states are part of the definition of done, and every data change ships with its rollback.
enters as
A spec plus approved copy
leaves as
A branch, a rollback plan, an a11y pass
stage 05Sieve + Ledger
Quality
Acceptance criteria run as tests across six devices and a real checkout path, plus visual regression against the last shipped build. Ledger sets the success metric here, before anything goes live.
enters as
A branch claiming to be done
leaves as
A test run, a visual diff, a metric plan
stage 06You
Human gate
The ticket arrives as a diff with the reasoning attached: what changed, why, what it is measured against, and what happens if it fails. Approve, edit or reject.
enters as
A tested diff with a metric plan
leaves as
An approval, an edit, or a rejection
stage 07Relay
Ship + watch
Merge, deploy behind a flag, then watch error and conversion rates for the first hour. If either moves the wrong way, Relay reverts without asking and reopens the ticket.
enters as
An approved diff
leaves as
A live change under watch, or a clean revert
walkthrough
one real ticket, end to end
AtlasTicket #4192: mobile ATC buried on PDP. 3 pts, p1.intake
MuseSpec: sticky ATC bar, 3 states, 44px target, safe-area inset.design