DRAFT — NOT SENT. Do not send or book until the room is confirmed; this is a prepared invitation only.

Subject: Launch review — Tue Oct 27, 2026, 14:00–14:45 Pacific (21:00–21:45 UTC), Room C

Required attendees:
- Maya (lead)
- Theo (engineer)
- Jules (design)

Optional:
- Nora (support). Her only availability is 10:00–11:00 Pacific, so she cannot attend this slot; per Maya's Oct 26 update she will read the notes instead. Her absence does not block the meeting.

When: Tuesday, October 27, 2026
- Main review: 14:00–14:45 Pacific (UTC−7) = 21:00–21:45 UTC
- Decision follow-up (Maya + Jules only): 14:45–15:00 Pacific = 21:45–22:00 UTC, remote (Room C is only free until 14:50)

Where: Room C (main review); follow-up remote.

Pre-meeting logistics (no action for most attendees):
- Theo: prep 13:30–14:00 Pacific (20:30–21:00 UTC), immediately before the review.
- Separate assistant: Room C setup 13:50–14:00 Pacific (20:50–21:00 UTC); setup overlaps Theo's prep by design.

Agenda (45-minute main review):
1. Launch readiness check — engineering status (Theo) and design status (Jules) (15 min)
2. Beta flag security question — review status of the required security-owner decision on enabling the beta flag; owner still unidentified (10 min)
3. Open risks, support readiness, and go/no-go criteria (15 min)
4. Recap actions and owners (5 min)
Then: 15-minute decision follow-up with Maya and Jules (remote), immediately after.

Open item before the meeting: the security owner must be identified and a decision obtained on whether the beta flag can be enabled (per Maya's update, Oct 26, 16:00 Pacific). Maya is not assumed to be the security approver. Please reply if you can help route this.

Notes will be shared with Nora afterward.
