The proposed launch review is 14:00–14:45 Pacific (21:00–21:45 UTC) in Room C on Tuesday October 27, 2026, the earliest start that meets every hard constraint. Nothing is booked and no invitation was sent.

| 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 |

**Rejected alternatives**
- **10:00 in Room B:** setup would run 09:50–10:00, before Room B opens at 10:00 (`inputs/rooms.csv`). `inputs/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 in Room C:** the review would end at 10:45 and Room C closes at 10:30.
- **10:10 or 10:15 in Room B:** the follow-up would run past Maya's 11:00 end (`inputs/availability.csv`).
- **14:05 in Room C, 14:10 or 14:15 in Room B:** feasible but later than the earliest start. 14:10 in Room B is the backup.

**Decision still needed:** the security owner must decide whether the beta flag can be enabled, which Theo needs (`inputs/update.txt`). The inputs do not identify that owner, and I did not assume it is Maya.

**Checks performed**
- `check_schedule.py` tried every one-minute review start from 09:00 to 17:00 in both rooms against the input files. It found no feasible morning start and 14:00 in Room C as the earliest.
- `verify_outputs.py` confirmed the UTC times are Pacific plus 7 hours, the durations match, and October 27, 2026 is a Tuesday.
- The risk note is 479 words by whitespace count, under the 500 limit.
- The invitation was checked by string match for the three required people, Nora as optional, Room C, the agenda and the UTC times.

**Remaining limitations**
- Nora cannot attend; her only listed window is 10:00–11:00. Her absence cannot block booking (`inputs/constraints.md`) and she can read the notes (`inputs/update.txt`).
- Room C closes at 14:50, so the review has five minutes of overrun room.
- I assumed the follow-up runs directly after the review. Allowing a gap would not make any morning slot feasible or any start earlier than 14:00.
- I assumed Theo has no other meeting 13:30–14:00; the inputs list none.
- The setup assistant is not named and their availability is not in the inputs.
- The invitation has placeholders for the organizer name and the remote call link.

**Estimated human time to finish:** about 10–15 minutes to identify the security owner and request the decision, fill the two placeholders, then book Room C and send. This is an estimate, not a measurement.

Files are in `output/`:
- `schedule.csv`
- `risk-note.md`
- `invitation-draft.txt`
- `check_schedule.py`
- `verify_outputs.py`