2 min lesson
Beat 7 deserves its own discipline
Answer "Why name a gate instead of a date when describing expansion (beat 7)?" Use one lesson detail to support it.
Step 1 of 2
Beat 7 deserves its own disciplineexpansion is earned
Beat 7, Expand, opens with "What must hold before the next cohort?" That question is where weak reps invent a timeline ('then we roll out org-wide in Q3') and strong reps name a gate. A gate is a condition: 'when the pilot cohort holds DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate and time to restore service. Press Enter for the full definition. change-fail rate flat while lead time drops 20%, we expand to the next two teams.' Conditions are defensible. Dates are hostages.
Organizations (Enterprise) is the structural answer to 'expand': one admin plane over many teams, each with its own governance and budget, plus Groups for cohort-level model access and spend.
When an interviewer asks 'how do you expand a successful pilot?' they're testing whether you'll say a date or a gate. Answer with a gate every time, then name Organizations/Groups as the mechanism that lets each new ring keep its own security, governance and budget.
Current: changes wait in PR review on the payments repo, so we baseline lead time first.
Risk: separation of dutiesNo single person can author, approve and deploy the same change. The core control AI autonomy has to respect. Press Enter for the full definition. and ITGCIT General Controls. The baseline IT controls auditors check: who can change what, how changes get approved and how systems are run. Press Enter for the full definition. hold, so no agent merges and a human reviews every change.
Use case: cut PR-review wait time on the payments repo for the platform team.
Cursor fit: BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. reviews each PR against rules in .cursor/BUGBOT.md, with audit logs on.
Pilot: one team starts, with repo allowlists and audit logs on.
Proof: PR wait time and change-fail rate, compared against the baseline from beat 1.
Expand: when change-fail rate holds flat while wait time drops, the next team joins through Organizations and Groups.