McRitchie Studio

Agent Context

Adopted 2026-06-26 (operator). Re-home the review lane so the PRIMARY reviewer owns it end-to-end via NESTED sub-agents (replaces the flat peer-spawn of avi + 2 seniors). FLOW with Avi placement DECIDED = Option B (2026-06-26): (1) Conductor -> AVI as a THIN delegation pre-step: Avi confirms the PR is acceptance-worthy (product/PO lens) AND picks the primary+light pair via reviewer-select. (2) Hand off to the PRIMARY as a sub-agent with ALL the technical-review goals: deep review of diff-vs-acceptance + code standards + smell + scalability, confirm base tiers green, drive-to-reviewed, and OWN the merge into release. (3) The PRIMARY spawns the LIGHT reviewer as ITS OWN sub-agent, so the primary holds full context when the light verdict returns. (4) Both complete and NEITHER flags a blocker -> the primary moves the task to reviewed and runs the merge into release (today the conductor runs bin/release merge; this gives the primary that responsibility). Option B keeps product-acceptance (Avi/PO) DISTINCT from technical review (the senior), preserving the PO lens and 'acceptance checked twice'. Roles sourced from config/devops_vocabulary.yml reviewer_roles (primary/light). DEPENDS ON reviewer-roles-primary-light landing first. This resolves the 'primary owns the merge' divergence the SOP flags on the Release Branch node; the Main Branch divergence was resolved as a no-op (it is the merge-forward guard).