McRitchie Studio
Say Hi 👋
Agents Builders
← Stages · Deployments

DevOps SOP

accountability swimlanes

The cycle as accountability lanes — one row per owner, steps flowing left → right. Node colors mark the kind of step; amber ◇ pulses are live intent markers (who's on it right now). Click any step to expand its Owner, Expectation, and Gate. A ⚠ flags where this picture differs from the implemented model.

Owner = the agent accountable for the whole lane: checks in at the start (intent event), runs the tests and steps in the middle, and updates the status at the end.

▦Stage ⌗Test Suite 👁Review ⇄Merge ⊳Deployment ◇Pulse ●Stage Update
B
Builder Build
→
→
→
◇ Pulse Builder on it
Owner
Builder (the per-task agent; its Pokemon mascot IS the build intent)
Expectation
Live intent: the task's Pokemon mascot — the build is claimed and in flight.
Gate
—
▦ Stage Building
Owner
Builder (the per-task agent; its Pokemon mascot IS the build intent)
Expectation
Build to the accepted criteria; write the shape's test tiers as you go (unit-first; a bug gets its red regression test first).
Gate
self-paced
⌗ Test Suite PR Review
Owner
Builder (the per-task agent; its Pokemon mascot IS the build intent)
Expectation
Certify the FULL suite + FULL rubocop green at the exact tree (fingerprint-bound).
Gate
bin/full-suite-check then bin/dor-check
● Stage Update Submitted
Owner
Builder (the per-task agent; its Pokemon mascot IS the build intent)
Expectation
Open the PR (base release) led by the task URL; record checks_run; move to submitted.
Gate
self-gate, then hands off to review
P
Primary Reviewer Review
→
→
→
→
→
◇ Pulse Reviewers on it
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
Live intent: reviewer-select records the primary + light pair the moment Avi kicks off review.
Gate
—
⌗ Test Suite PR Review
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
Confirm the shape's base tiers (unit/component) are green for the change.
Gate
base tiers green
👁 Review Visual
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
The PRIMARY runs the deep pass (diff-vs-acceptance, code standards, smell, scalability) and spawns the LIGHT reviewer as its own sub-agent for a focused pass.
Gate
2 approvals (primary + light), else block with qa_feedback
⇄ Merge Release Branch
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
The PRIMARY reviewer runs bin/release merge to land the PR in the persistent release branch; membership flips reviewed to assembled. The primary owns the merge — not a separate conductor step.
Gate
deterministic; a conflict surfaces here
⌗ Test Suite Merge Review
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
Confirm the merge is clean on origin/release (integrating broke nothing).
Gate
green on origin/release
● Stage Update Reviewed
Owner
Primary Reviewer (the PRIMARY reviewer owns the whole lane: the deep-pass senior picked per task (most domain depth, usually the longest step) who spawns the LIGHT reviewer as its own sub-agent for a focused second pass, then on two approvals drives the task to Reviewed AND runs the merge. Avi is a thin delegation pre-step: he confirms product-acceptance and picks the pair, then hands the lane to the primary.)
Expectation
The PRIMARY reviewer drives the status to Reviewed, then runs the merge.
Gate
2 approvals (primary + light)
S
Steffon Assemble
→
→
→
→
→
◇ Pulse Steffon on it
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
Live intent: bin/release prepare records Steffon's QA intent over every release member.
Gate
—
⌗ Test Suite Merge Review
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
Run the next tier (integration + an e2e-smoke) on origin/release.
Gate
regression blocks the task
⇄ Merge Main Branch
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
Merge-forward guard: if main moved ahead, merge main into release so release always keeps main as an ancestor (stays shippable). Main itself does NOT move here — it advances only at ship, when release fast-forwards into main.
Gate
release stays ahead of main
⊳ Deployment QA
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
bin/release prepare: deploy origin/release to the QA app, then poll /up.
Gate
wait_for_boot returns 200
⌗ Test Suite QA Acceptance
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
The QA tier (integration + e2e-smoke) is green on the deployed candidate.
Gate
deterministic suite
● Stage Update Assembled
Owner
Steffon (Platform Engineer. Owns from Reviewed: checks in, runs the QA tier and deploys, updates the status to Assembled. This lane IS the execution of 'assembling'.)
Expectation
Steffon updates the status to Assembled: the QA candidate is ready.
Gate
QA booted and suite green
A
Avi Ship
→
→
→
→
→
◇ Pulse Avi on it
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
Live intent: bin/release ship records Avi's ship intent over every release member.
Gate
—
⌗ Test Suite QA Acceptance
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
Avi runs the full e2e + highest tier on the FROZEN ship SHA (the exact prod commit).
Gate
avi_ship_gate aborts on any failure
👁 Review Visual
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
Avi re-confirms the acceptance criteria on the frozen SHA (checked twice by design).
Gate
—
⊳ Deployment Prod
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
Fast-forward release to main per repo, deploy, smoke /up, run post_deploy_cmd.
Gate
the ONE operator gate: after Avi's tests, before the deploy
● Stage Update Shipped
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
Members flip to Shipped; release notes auto-post.
Gate
production /up 200
⌗ Test Suite Smoke Test
Owner
Avi (Owns the ship: runs the full e2e on the frozen ship SHA, then stops for the operator's go before prod.)
Expectation
production-smoke-seal kicks the tires on prod (read-only @qa-readonly) and stamps a seal.
Gate
seal alert (non-blocking)
Ref
PR

Click any step for its Owner · Expectation · Gate. The ⚠ points are where this model and the implemented code still diverge — the diagram is where we reconcile them.