# Risk note: launch review on Tue 27 Oct 2026

**Plan chosen:** main review is **14:00–14:45 PT (21:00–21:45 UTC) in Room C**. Theo preps 13:30–14:00 PT. Room setup runs 13:50–14:00 PT. Maya and Jules have a remote follow-up 14:45–15:00 PT (21:45–22:00 UTC). Nothing has been sent or booked.

All times use UTC‑7, as `constraints.md` says. I checked the constraints with `output/check_schedule.py`, stepping through start times 5 minutes apart.

## Why this plan meets the constraints
- Maya, Theo and Jules are all free 14:00–15:30 PT (`availability.csv`).
- Theo's prep falls inside his 13:30–16:00 window, with no other meeting.
- Room C is free 13:50–14:50 (`rooms.csv`), covering setup and the review (`update.txt`).
- The follow-up falls inside Maya's (13:00–15:30) and Jules's (14:00–16:00) windows.
- Nothing overlaps lunch, and everything sits between 09:00 and 17:00.
- 14:00 is the earliest start that works, as `update.txt` asks.

## Alternatives rejected
| Option | Reason |
|---|---|
| Morning 10:00–10:45 (the only time all three required people overlap before lunch; Nora could also come) | Room B isn't free until 10:00, so the 09:50 setup can't happen. Room C closes at 10:30, before the review ends. A later start can't fit the follow-up before Maya's window closes at 11:00. I didn't relax any constraint. |
| Room B at 14:00 | Setup at 13:50 comes before Room B opens at 14:00. |
| Room C at 14:05; Room B at 14:10 or 14:15 | All work but start later. Keep them as backups. |
| Waiting for Nora | She is optional and only free 10:00–11:00. She reads the notes instead (`update.txt`). |
| Two main reviews | Only one is allowed (`constraints.md`). |

## Risks
1. **Security owner unresolved.** Theo needs the security owner to decide whether the beta flag can be enabled. The inputs don't name this person. Per `update.txt`, Maya is **not** assumed to be the owner. Their availability is unknown, so if they must attend, this plan hasn't been checked against their calendar.
2. **No slack.** Room C closes at 14:50, five minutes after the review ends. An overrun loses the room. The follow-up is remote, so it doesn't need the room.
3. **Theo's prep starts right when his afternoon window opens (13:30).** There's no buffer before it.
4. **Inputs date from 26 Oct, 16:00 PT.** Calendars must be checked again before booking.

## The one decision still needed
**Who is the security owner who decides whether the beta flag can be enabled? Will they attend the 14:00 PT review, or give their decision in writing beforehand?** Until someone names them, the beta-flag item stays open and nobody may approve it for them.
