# Risk note — launch review, Tuesday October 27, 2026

## Chosen plan (earliest feasible, per inputs/update.txt)
- 13:30–14:00 PT (20:30–21:00 UTC): Theo prep (30 min, immediately before review).
- 13:50–14:00 PT (20:50–21:00 UTC): Room C setup by separate assistant (may overlap prep, inputs/constraints.md).
- 14:00–14:45 PT (21:00–21:45 UTC): main review, Room C; Maya, Theo, Jules required.
- 14:45–15:00 PT (21:45–22:00 UTC): decision follow-up, remote, Maya + Jules — same availability windows as the review (Maya 13:00–15:30, Jules 14:00–16:00, inputs/availability.csv). Remote because Room C closes 14:50 (inputs/rooms.csv); follow-up may be remote (inputs/constraints.md).

Pacific = UTC−7 per inputs/constraints.md. Verified by exhaustive grid search of all constraints at both 5-minute and 1-minute resolution (check_schedule.py, review_audit.py); all input boundaries are 5-minute aligned, so no earlier feasible start can be missed.

## Rejected alternatives
- **Morning 10:00–10:45**: the only morning start satisfying people constraints — Jules opens 10:00; Theo's prep forces start ≥10:00; Maya's 11:00 close forces review+follow-up (60 min) to start ≤10:00. But no room works: Room B opens 10:00, so 09:50–10:00 setup violates "room free throughout setup and main review" (inputs/update.txt); Room C closes 10:30, before the 10:45 review end. Rejected; constraint not relaxed.
- **13:30 start**: Jules unavailable until 14:00; Theo's prep would run 13:00–13:30, outside his availability.
- **Later starts (14:01–14:05 Room C; 14:10–14:15 Room B)**: all feasible but later; update.txt requires the earliest start. Any start after 14:15 fails room windows.

## Risks and assumptions
1. **Zero setup buffer**: setup starts exactly when Room C opens (13:50). Any room-calendar slip breaks the plan; fallback is Room B at 14:10 PT (21:10 UTC), still same-day feasible.
2. **Thin review buffer**: review ends 14:45 vs Room C close 14:50 (5 min). Overrun forces the follow-up fully remote — already planned remote.
3. **Nora absent**: her only window is 10:00–11:00 (inputs/availability.csv). Optional per inputs/constraints.md; she reads notes (inputs/update.txt). Support questions may go unanswered live.
4. **Assumption — Theo's prep**: availability windows are treated as meeting-free; no separate calendar was supplied, so "without overlap with another meeting" is verified only against availability. Confirm with Theo.
5. **Assumption — "same available window"**: interpreted as Maya's and Jules's windows containing the review; the follow-up sits inside both.
6. Nothing has been booked or sent; room and assistant availability are per the supplied CSVs only.

## One decision still needed
Whether the **beta flag can be enabled** — this requires a decision from the **security owner, who is not identified in the material** (inputs/update.txt). Maya is not assumed to own security approval. Identify the owner and obtain the decision before or at the review; Theo is blocked on it.
