build-retention-pulselisted

# /build-retention-pulse — Cross-Cohort Program Retention Pulse > **Purpose.** Retention check across cohorts (program-side). Different from `/program-cohort-pulse` (which is weekly health for a single active cohort). This is monthly/quarterly retention analysis: completion rates, refund rates, graduate referrals, alumni-to-retainer conversion, NPS. Outputs the cohort-2 launch-readiness gate. > > **Bar.** Cohort 2 should not launch until cohort 1 hits the readiness threshold. Sales pressure trying to launch early without the metrics = cohort 2 refunds + brand damage. The pulse is the gate. ## When to invoke - **Cron — 1st of each month at 11:00 (program-tier active).** Per `paperclip.manifest.yaml`. - Quarterly cross-cohort review (program-head + operator) - Before any cohort-2/3/N launch decision - Before annual program-tier strategy review ## Required inputs 1. `program.cohorts` data — every cohort's enrollment, completion, refund, and outcome data 2. `program.students.{slug}` data per cohort — first-win achievements, completion status, post-cohort outcomes 3. Refund records + reasons 4. Alumni-to-retainer conversion data (program graduates who became DFY clients) 5. Graduate-referral data (graduates who referred next-cohort enrollees) 6. NPS survey responses (week 12 + 6-month follow-up) ## The pulse sequence ### Step 1 — Scope selection | Scope | Use case | |---|---| | `active-cohort` | Current cohort mid-flight (typically week 4-12) | | `prior-cohort` | Specific