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

Status: proposal only. Nothing is booked and no invitation has been sent.

## Chosen plan (Pacific = UTC-7, per constraints.md)

| Block | Pacific | UTC | Who / where |
|---|---|---|---|
| Theo prep | 13:30–14:00 | 20:30–21:00 | Theo |
| Room setup | 13:50–14:00 | 20:50–21:00 | Assistant, Room C |
| Main review | 14:00–14:45 | 21:00–21:45 | Maya, Theo, Jules; Room C |
| Decision follow-up | 14:45–15:00 | 21:45–22:00 | Maya, Jules; remote |

This is the earliest start that meets every hard constraint, as update.txt requests. The three required people overlap only 10:00–11:00 and 14:00–15:30 (availability.csv).

## Rejected alternatives

| Option | Why rejected |
|---|---|
| 10:00, Room B | Setup 09:50–10:00 falls before Room B opens at 10:00 (rooms.csv). update.txt says the room must be free throughout setup. Everything else fits and Nora could attend, but I did not relax the rule. |
| 10:00, Room C | Review would end 10:45; Room C closes 10:30. |
| 10:10 or 10:15, Room B | Review ends 10:55 or later; the 15-minute follow-up would run past Maya's 11:00 end. |
| Before 10:00, Room C | Jules is unavailable until 10:00; Theo's prep would start before 09:30. |
| 14:00, Room B | Setup 13:50–14:00 falls before Room B opens at 14:00. |
| 14:05 Room C; 14:10 or 14:15 Room B | Feasible, but later than the earliest start. 14:10 Room B is the backup. |
| After 14:15 | Neither room covers setup plus review. |

## Decision still needed

The security owner must decide whether the beta flag can be enabled; Theo needs this (update.txt). The inputs do not identify that owner, and Maya is not assumed to hold security approval. Until someone names the owner and gets the decision, this item is unresolved and the review may not be able to close it.

## Risks

- **No slack at the start.** Theo's prep begins the minute his window opens, Room C setup begins the minute the room opens, and Jules becomes available at 14:00.
- **Five minutes of overrun room.** Room C closes at 14:50. The follow-up is remote for that reason.
- **Nora cannot attend.** Her only listed window is 10:00–11:00. constraints.md says her absence cannot block booking, and update.txt says she can read the notes.
- **Setup assistant.** The inputs do not name the assistant or give their availability.

## Assumptions

- The follow-up runs directly after the review. Allowing a gap would not make any morning slot feasible, nor any start earlier than 14:00.
- "Same available window" means the availability block containing the review (Maya 13:00–15:30, Jules 14:00–16:00).
- Theo has no other meeting 13:30–14:00; the inputs list none.
- Where update.txt (October 26, 16:00) is stricter than constraints.md on setup, the update governs.
