# 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 / UTC)

| Block | Pacific | UTC | Where | Who |
|---|---|---|---|---|
| Theo prep | 13:30–14:00 | 20:30–21:00 | not specified | Theo |
| Room setup | 13:50–14:00 | 20:50–21:00 | Room C | assistant |
| Main review | 14:00–14:45 | 21:00–21:45 | Room C | Maya, Theo, Jules |
| Decision follow-up | 14:45–15:00 | 21:45–22:00 | Remote | Maya, Jules |

This is the earliest start that meets every hard constraint, as Maya asked (update.txt). The offset comes from constraints.md.

## Rejected alternatives

- **Room B, 10:00 review.** All three are free 10:00–11:00 (availability.csv), but setup would run 09:50–10:00 and Room B opens at 10:00 (rooms.csv). update.txt says the room must be free throughout setup. I did not relax this, although it is the only slot Nora could attend.
- **Room B, 10:10 review.** Setup fits, but the review ends 10:55 and the follow-up would run to 11:10; Maya's window ends 11:00.
- **Room C, morning.** Room C closes at 10:30 and Jules starts at 10:00, so a 45-minute review cannot fit.
- **Any afternoon start before 14:00.** Jules starts at 14:00, and Theo's prep cannot begin before 13:30.
- **Room B, 14:10 review.** Feasible (prep 13:40–14:10, setup 14:00–14:10, review to 14:55, follow-up to 15:10) but ten minutes later. Kept as the fallback.

## Decision still needed

Theo needs the security owner's decision on whether the beta flag can be enabled (update.txt). The owner is not identified in any input, and Maya must not be assumed to hold that approval. Someone must name the owner and obtain the decision. The inputs do not say whether the review can proceed without it.

## Risks

- **No slack in Room C.** Only starts between 14:00 and 14:05 work. A later start runs past 14:50, when the room closes.
- **Tight arrivals.** Theo's prep starts the minute his window opens, and Jules's window opens at review start.
- **Nora will be absent.** Her only window is 10:00–11:00. She is optional and can read the notes (constraints.md, update.txt), so someone must take notes.
- **Short notice.** The update arrived October 26 at 16:00 Pacific. Room and calendar data may have changed since.
- **Fallback is narrow.** Room B works only for starts between 14:10 and 14:15.

## Assumptions

- Theo's prep must sit inside his availability window.
- The follow-up starts immediately after the review; the inputs say only "after" and "within the same available window".
- Availability windows are treated as free time. I had no calendar view of other meetings.
- The setup assistant is unnamed, and their availability is not in the inputs.
