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

## Chosen plan
Room C, main review **14:00–14:45 Pacific (21:00–21:45 UTC)**. Theo prep 13:30–14:00 PT; assistant room setup 13:50–14:00 PT; remote Maya+Jules decision follow-up 14:45–15:00 PT (21:45–22:00 UTC). Pacific = UTC−7 per inputs/constraints.md. This is the earliest feasible start with all required attendees, as Maya demanded (inputs/update.txt). Verified by exhaustive 5-minute-grid check of all rooms/starts against inputs/availability.csv and inputs/rooms.csv (work/check_schedule.py).

## The one decision still needed
**Who is the security owner, and can the beta flag be enabled?** Theo needs this decision before launch (inputs/update.txt). The owner is not identified in any supplied input, and update.txt explicitly says not to assume Maya owns security approval. This remains **unresolved**; someone must name the owner and obtain the decision. It is not resolved by this schedule.

## Rejected alternatives (constraint citations)
- **Room B morning, review 10:10–10:55** (earliest B start: room opens 10:00, rooms.csv; 10-min setup): follow-up 10:55–11:10 exceeds Maya's morning window ending 11:00 (availability.csv). No later morning slot fits. Rejected: follow-up constraint (constraints.md).
- **Room C morning, review 10:00–10:45** (Jules starts 10:00, availability.csv): Room C morning availability ends 10:30 (rooms.csv); room must be free through setup + review (update.txt). Rejected.
- **Any start before 10:00**: Jules unavailable (availability.csv). Any 11:00–14:00 start: lunch 12:00–13:00, room gaps, and Theo/Jules/Maya window gaps rule these out (grid check).
- **Room C 13:50 start**: room opens 13:50, so setup cannot finish by 13:50; Jules also unavailable until 14:00.
- **Room B 14:10–14:55 afternoon**: fully feasible, but 10 minutes later than Room C 14:00; update.txt requires earliest, so rejected in favor of C.
- **Nora attendance at any feasible time**: impossible — her only window is 10:00–11:00 (availability.csv), which no feasible review overlaps. She is optional and cannot block booking (constraints.md); she will read the notes (update.txt).

## Risks
1. **Security approval unresolved** (above) — could block launch regardless of a valid meeting slot.
2. **Zero room slack**: Room C afternoon block is 13:50–14:50 (rooms.csv); setup starts exactly at 13:50 and review ends 14:45, leaving 5 minutes. Any setup delay or review overrun past 14:50 loses the room; follow-up is remote, so it survives an overrun (Maya free to 15:30, Jules to 16:00).
3. **Support absent**: Nora cannot attend; support questions must be handled asynchronously via notes.

## Assumptions (inputs do not resolve)
- "Same available window" for the follow-up = the shared Maya/Jules afternoon windows containing the review; follow-up scheduled immediately after (14:45–15:00), which fits either reading.
- Theo's prep must sit inside his own availability window with no conflicting meeting; none is listed in inputs.
- Candidate starts evaluated on a 5-minute grid; all input times are 5/10-minute aligned, so no feasible earlier start is missed.

Nothing has been booked or sent; this is a draft plan only.
