I found no errors in the plan itself, but fixed several problems in the files. The review stays on Tue 27 Oct 2026 at 14:00–14:45 PT (21:00–21:45 UTC) in Room C. Theo preps from 13:30, setup starts at 13:50, and Maya and Jules have a remote follow-up from 14:45 to 15:00. The original submission is saved unchanged in `output/original_submission/`.

**Change log:**
1. **`schedule.csv`:**
   - Times were free text that couldn't easily be imported; they are now standard ISO times (e.g. `2026-10-27T13:30-07:00` and `2026-10-27T20:30Z`).
   - I had made up a location for Theo's prep ("Theo's own workspace"); it now says no room is required by the inputs.
   - Sources now cite the specific rows.
   - It notes that the setup assistant's availability isn't in the inputs.
2. **`invitation-draft.txt`:**
   - "A separate invitation will be sent" implied an action; it now says the follow-up still needs its own calendar hold, not yet created.
   - It lists what must happen before sending: book Room C 13:50–14:45 and name the security owner.
   - The beta-flag agenda item now says the owner isn't assumed to be Maya.
3. **`risk-note.md`:**
   - Added row-level citations and the exact Room C booking window.
   - Added that the inputs don't say whether the missing security decision blocks the review itself.
   - It is now 473 words.
4. **New `verify_outputs.py`:** a script that checks the revised schedule against every hard constraint and the invitation's required contents.

**Checks performed:**
- **Feasibility search:** I re-ran `check_schedule.py`, which tries every 5-minute start. It found the same four workable starts (Room C at 14:00 or 14:05, Room B at 14:10 or 14:15), and 14:00 in Room C is still the earliest.
- **Constraint check:** `verify_outputs.py` reported 0 failures. It checks:
  - date, the UTC-7 offset and that the UTC times match
  - working hours and lunch
  - 45-minute review in Room B or C
  - 30-minute prep straight before, and 10-minute setup in the same room
  - the room is free throughout setup and review
  - required people are available
  - the follow-up is in the same availability window as the review for Maya and Jules
  - Nora is optional (she isn't available then)
  - the risk note is under 500 words
  - the invitation includes the required items
- **Source conflicts:** none found, so no constraint was relaxed.

**Decision still needed:** someone must name the security owner who decides whether the beta flag can be enabled.

**Remaining limitations:**
- Nothing is booked or sent.
- Room availability is a snapshot.
- The setup assistant's availability is unknown.
- The schedule has no slack: Room C is released at 14:50, five minutes after the review ends.

**Estimated human time to finish:** about 15–25 minutes (an estimate, not measured).

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