# Risk note — launch review, Tue 27 Oct 2026

## Recommended plan (proposed only; nothing booked or sent)
- Theo prep: 13:30–14:00 PT (20:30–21:00 UTC)
- Room C setup: 13:50–14:00 PT (20:50–21:00 UTC)
- Review, Room C: 14:00–14:45 PT (21:00–21:45 UTC)
- Maya + Jules follow-up, remote: 14:45–15:00 PT (21:45–22:00 UTC)

PT = UTC-7 (`constraints.md`). This is the earliest start that meets every hard constraint, as Maya asked (`update.txt`). I checked this by testing every 5-minute start from 09:00 to 17:00 (`check_schedule.py`).

## Rejected alternatives
- **Morning.** All three required people are free only 10:00–11:00 (`availability.csv`). The review and follow-up need 60 minutes, so the review would have to run 10:00–10:45.
  - Room B opens at 10:00, so setup (09:50–10:00) can't happen there. The room must be free during setup (`update.txt`).
  - Room C closes at 10:30 (`rooms.csv`).
- **Room C at 14:05.** Works, but it isn't the earliest start.
- **Room B at 14:10 or 14:15.** Works, but starts later. **Backup** if Room C is lost — Room B:
  - prep 13:40–14:10
  - setup 14:00–14:10
  - review 14:10–14:55
  - follow-up 14:55–15:10 PT
- **Fitting Nora (10:00–11:00).** Not possible, because the morning fails on rooms. Nora is optional (`constraints.md`) and can read the notes (`update.txt`).
- **No constraints were relaxed.** Setup wasn't shortened, Theo's prep doesn't overlap another meeting, and nothing uses lunch (12:00–13:00).

## Risks
1. **Security decision (the one decision still needed).** Theo needs the security owner to decide whether the beta flag can be enabled. That person isn't named in the inputs, and `update.txt` says not to assume it's Maya. Someone must name the owner and get their decision, ideally before 14:00 PT. Until then the beta-flag item stays open. No security approver is named or invited.
2. **No slack.**
   - Setup starts when Room C opens (13:50).
   - Prep starts when Theo becomes available (13:30).
   - If the review overruns, Room C is released at 14:50, only 5 minutes after the planned end. The follow-up is remote, so it doesn't need the room.
3. **Room data is a snapshot.** Room C has not been booked. A human must book it; if that fails, use the Room B backup.
4. **Time zone.** UTC times use the exercise's fixed UTC-7 offset.
5. **Follow-up timing.** The follow-up must end by 15:30, when Maya's window closes. If the review overruns by more than 30 minutes, it won't fit.

## Assumptions
- Theo's prep is solo and falls within his available hours.
- "Same available window" means the follow-up is in the same availability block as the review for both Maya and Jules.
- The setup assistant is available whenever needed. The inputs don't say.
