I've written the schedule, risk note and invitation draft. The plan puts the main review on Tue 27 Oct 2026 at **14:00–14:45 Pacific (21:00–21:45 UTC) in Room C**, the earliest time that meets every hard constraint. Nothing has been booked or sent.

| Item | Pacific (UTC-7) | UTC |
|---|---|---|
| Theo's prep (no other meetings) | 13:30–14:00 | 20:30–21:00 |
| Room C setup (by the assistant) | 13:50–14:00 | 20:50–21:00 |
| **Main review, Room C** | **14:00–14:45** | **21:00–21:45** |
| Maya + Jules follow-up, remote | 14:45–15:00 | 21:45–22:00 |

**Why the morning doesn't work:** Maya, Theo and Jules are all free together only from 10:00 to 11:00 (`availability.csv`). The review plus the 15-minute follow-up has to fit in that hour, so the review would run 10:00–10:45.
- Room B opens at 10:00, so there's no free room for the 09:50 setup (`update.txt` says the room must be free during setup).
- Room C closes at 10:30, before the review would end (`rooms.csv`).

**Rejected alternatives:**
- **Room C at 14:05:** works, but isn't the earliest start, which Maya asked for in `update.txt`.
- **Room B at 14:10 or 14:15:** works, but starts later. Room B at 14:10 is the backup if Room C can't be booked.
- **Moving the review so Nora can attend:** not possible, since her only free hour is 10:00–11:00 and the morning fails. She's optional and will probably get the notes instead.

I didn't relax any constraint: setup is the full 10 minutes, Theo's prep doesn't overlap another meeting, and nothing uses the 12:00–13:00 lunch.

**Decision still needed:** someone must name the security owner who decides whether the beta flag can be enabled. Nobody is identified in the inputs, and `update.txt` says not to assume it's Maya. The invitation leaves this as an open agenda item and doesn't name or invite an approver.

**Checks performed:**
- A script tested every 5-minute start from 09:00 to 17:00 in both rooms. Exactly four starts work: Room C at 14:00 or 14:05, and Room B at 14:10 or 14:15.
- The risk note is 445 words, under the 500 limit.
- `schedule.csv` reads as a valid CSV with 4 rows.
- I didn't use the browser, since this task has no site.

**Remaining limitations:**
- Room availability comes from a calendar snapshot; no room is held.
- The setup assistant's availability isn't in the inputs. I assumed they're free.
- I treated Theo's prep as solo time that must fall within his available hours.
- I read "same available window" to mean the follow-up falls in the same availability block as the review for both Maya and Jules.
- The schedule has no slack: setup starts when Room C opens, and the room is released 5 minutes after the review ends.

**Estimated human time to finish:** about 15–25 minutes to identify the security owner, book Room C, and review and send the invitation (an estimate, not measured).

Files are in `output/`:
- `schedule.csv`
- `risk-note.md`
- `invitation-draft.txt`
- `check_schedule.py` (the feasibility check)
- `wc.py` (word and row count helper)