Capacity Planning: The Team Wants to Ship Biweekly

Leadership asks whether the monthly RLHF release cadence can move to biweekly. Current state: RL training (rollout generation + FSDP learner updates) takes ~9 days of the ~30-day cycle; annotation takes ~12 days (bounded by annotator throughput, not queueing); eval + human review of flagged regressions takes ~4 days; the remaining days are data sourcing, privacy filtering, and release/rollout mechanics.

1. Given these numbers, is a biweekly cadence achievable by simply "working faster," or does something structural have to change? Identify the binding constraint(s).
2. Propose one concrete lever for each binding constraint you identified, and be specific about the trade-off each lever makes.
3. Is there a stage in this pipeline that scales roughly for free with cadence, and one that emphatically does not? Name both and explain the difference.