Source of truth: toolkit/gates/README.md. Edit it there; this page is regenerated on build.
Gate cards
One card per gated transition — the six phase-transition gates of the RAPID pipeline, plus STOP Exit (entry into the pipeline from remediation), GTM Readiness (the commercial complement) and the intake gate (anything new entering the stack). Each card is a short checklist executed in minutes, not committees — entry/exit criteria, the evidence required, what CI automates versus what a human signs, and who can (and cannot) waive it.
The gate model — why these exist and how they keep speed safe — is documented in the handbook: The process → Gates.
| Gate | Transition | Card |
|---|---|---|
| Definition of Ready | Definition → Design | definition-of-ready.md |
| Design Review | Design → Tech selection / Build | design-review.md |
| Tech Selection sign-off | Tech selection → Build | tech-selection.md |
| Merge gate | within Build, every PR | build-merge.md |
| Refinement Exit | Refinement → Flow-state / Production | refinement-exit.md |
| Production Readiness | Flow-state → Production | production-readiness.md |
| STOP Exit — "Definition of Stable" | STOP → RAPID pipeline eligible | stop-exit-definition-of-stable.md |
| GTM Readiness | product built → sellable / launchable | gtm-readiness.md |
| Intake | anything new entering the stack | intake.md |
| CXsmart Scale-up | StudyBuddy proven → pattern applied to CXsmart | cxsmart-scale-up.md |
New or amended cards start from gate-card-template.md.
Waivers. Every gate has a documented, logged waiver path: time-boxed, with a named approver, recorded so that speed pressure bends the process visibly rather than silently. A waiver is never a way to skip a check permanently — it carries an expiry after which the gate re-blocks.