McRitchie Studio
Say Hi 👋
Agents Builders
← All Tasks
Sizing

DevOps SOP infographic

Shipped
devops-sop-infographic

Created

Jun 26, 20:53

Started

Jun 26, 20:53

Completed

Jun 26, 23:21

DevOps handoff

Type

Feature

Shape

ui-only

Worktree Slug

devops-sop-infographic

Repositories

mcritchie-studio

Release Train

—

Branch

feat/devops-sop-infographic

Pull Request

https://github.com/amcritchie/mcritchie-studio/pull/250

Local URL

http://localhost:3006/stages/sop

QA URL

—

Production URL

—

ui,docs

Acceptance Criteria

  • SOP infographic at stages/sop linked from admin dashboard
  • Vocabulary YAML is the single source of truth
  • Each step expands showing owner expectation and gate
  • Tracker step labels are distinct and unambiguous
  • Deploy dev toolbar steps a fixture release live
  • Pulses mark real intents one per lane

Expected Test Plan

  • [unit] Devops::Vocabulary loads YAML: 4 lanes, symbol types, one pulse per lane
  • [unit] release_tracker active labels are 5 distinct (no Testing/Deploying twice)
  • [component] GET /stages/sop 200: lane owners, owner-definition, expand detail
  • [integration] Dev::BoardController advance_release steps tracker done_count 0 to 5

Checks Run

  • [unit] test/models/devops/vocabulary_test.rb green: 4 lanes, symbol types, pulse fallback to stage
  • [unit] test/helpers/application_helper_test.rb green: 5 distinct tracker active labels
  • [component] test/controllers/tasks_controller_test.rb green: GET /stages/sop renders lanes + owner def + expand detail
  • [integration] test/controllers/dev/board_controller_test.rb green: advance_release done_count 0..5; reset clears; prod-gated
  • [suite] bin/full-suite-check green at 673fa1c902d5: 1929 runs 0 failures; rubocop 540 files clean
  • [full-suite@7ba9216a0e9bb016b13010db5e807065e2256f01] bin/rails test green
  • [rubocop@7ba9216a0e9bb016b13010db5e807065e2256f01] bin/rubocop clean

Agent Context

Operator wants their DevOps SOP THINKING rendered as a UI infographic, linked from the admin dashboard, as an 'opening gambit to reach understanding' — a living artifact to align the team's mental model. Render the operator's 2026-06-26 swimlane diagram FAITHFULLY (their thoughts), then visually flag where it diverges from current code so they can reconcile in-UI. FOUR accountability lanes (owner avatar/circle on the left, steps flowing left-to-right, lane wraps to next row): (1) BUILDER lane (unnamed = per-task Pokemon mascot): Building -> [TestSuite: PR Review] -> Submitted. (2) CARL lane (review): [TestSuite: PR Review] -> [Review: Visual] -> [Merge: Release Branch] -> [TestSuite: Merge Review] -> Reviewed. (3) STEF lane (assemble): [TestSuite: Merge Review] -> (Pulse: Testing) -> [Merge: Main Branch] -> (Pulse: Assembling) -> [Deployment: QA] -> (Pulse: Deploying) -> [TestSuite: QA Acceptance] -> (Pulse: Testing) -> Assembled. (4) AVI lane (ship): [TestSuite: QA Acceptance] -> [Review: Visual] -> [Deployment: Prod] -> (Pulse: Deploying) -> Shipped -> [TestSuite: Smoke Test]. NODE TYPES to color-code distinctly: Stage (rect), Test Suite (rect, ⌗), Review (rect, 👁), Merge (rect, ⇄), Deployment (rect, ⊳), Pulse (diamond/amber = the live INTENT marker), Stage Update (pill on the transition). DIVERGENCES from canonical to mark visually: single 'Carl' reviewer vs the real 2-senior heavy+light reviewer-select + Avi product-acceptance delegator; 'Merge Main Branch' shown in assemble lane but code only ff's main->release at SHIP; 'Smoke Test' final step == the production-smoke-seal-agent feature being built in parallel. Pulses == existing intent events/live ticker. New page (e.g. /stages/sop or extend the existing /stages stage guide); add a link from the admin dashboard. Iterate LIVE in the worktree preview (operator wants to react visually). Reuse studio-engine theme tokens for dark/light parity; Tailwind v4. Shape ui-only (presentation), dor_tier component; visual acceptance at the QA stop.

Stage Timeline

Who handled each stage, the time it took (measured), and the model / tokens / cost reported (best-effort) — plus who's on it right now. — means the agent didn't report that metric.

Sizing Avi · PO MEDIUM Dev MEDIUM Actual XL ≠ forecast
  1. Created → Designed
    M Machoke
    Machoke
    Model
    —
    Duration
    —
    Tokens
    —
    Cost
    —
    Completed Jun 26, 20:53 · about 13 hours ago
    api
  2. Designed → Building
    M Machoke
    Machoke
    Model
    claude-opus-4-8
    Duration
    under a minute
    Tokens
    1,399,016
    Cost
    ~$2.56
    Started Jun 26, 20:53
    Completed Jun 26, 20:53 · about 13 hours ago
    cli
  3. Building → Submitted
    M Machoke
    Machoke
    Model
    claude-opus-4-8
    Duration
    about 2 hours
    Tokens
    145,384,693
    Cost
    ~$98.20
    Started Jun 26, 20:53
    Completed Jun 26, 22:54 · about 11 hours ago
    cli
  4. Submitted → Reviewed
    C Carl
    Carl primary
    A Alex
    Alex light
    Model
    claude-opus-4-8
    Duration
    13 minutes
    Tokens
    —
    Cost
    —
    Started Jun 26, 22:54
    Completed Jun 26, 23:07 · about 11 hours ago
    cli
  5. Reviewed → Assembled
    S Steffon
    Steffon
    Model
    claude-opus-4-8
    Duration
    1 minute
    Tokens
    1,554,984
    Cost
    ~$1.02
    Started Jun 26, 23:07
    Completed Jun 26, 23:08 · about 11 hours ago
  6. Assembled → Shipped
    A Avi
    Avi
    Model
    claude-opus-4-8
    Duration
    13 minutes
    Tokens
    7,846,029
    Cost
    ~$5.59
    Started Jun 26, 23:08
    Completed Jun 26, 23:21 · about 10 hours ago

Conversation

QA review feedback, agent handoffs, and follow-up notes for this task.

Comment alex about 11 hours ago

Senior review -> APPROVED (2/2). Reviewers: Carl (backend/safety heavy) + Alex (SOP-accuracy light), both high confidence. 120 tests / 691 assertions green; all 6 acceptance met. SAFETY CONFIRMED: dev deploy toolbar is Rails.env.local?-gated (403 in prod, tested) and every mutation scoped to the dev_fixture marker -- never touches a real Release/board. Overlap with #249 (already in RC) on _release_summary.html.erb is CLEAN (#250 restyles bottom tracker dots; #249 header seal badge byte-identical). Infographic faithfully represents the documented model (owners/gates/one-operator-gate/pulses/stage names match sections 1.2/1.4; the 2 real divergences honestly flagged with a warning). Follow-ups (non-blocking): (1) MAJOR clarity (Alex) -- scannable tile labels reuse across lanes mislabel distinct gates: 'Visual' appears nowhere in the model; 'QA Acceptance' mislabels Avi's frozen-SHA e2e gate; 'PR Review'/'Merge Review' reused. One-file YAML rename recommended (expand panels accurate, so non-blocking but undercuts an understanding artifact). (2) docs not cross-referenced though the YAML header claims they are -- add a section-1.4 pointer. (3) designed/blocked/archived stages absent -- add a 'happy path' caption. (4) minor: stale comment tasks_controller.rb:43; hardcoded legend order. -> reviewed.

Sealed-bid sizing

Edit →

Alex (PM)

—

Avi (PO)

MEDIUM

Dev

MEDIUM

Actual

XL