# Field Notes — decision log and coordination plan

**As of:** October 20, 2026, 10:00 Pacific. **Draft only; nothing sent, approved, tested or published by this exercise.** All dates below are 2026 and all times are Pacific. The CSV distinguishes source deadlines from proposed coordination targets; date-only source deadlines have no invented hour.

## Evidence and precedence

- **B:** `inputs/01-original-brief.md`, “Original brief — October 14, 09:00 Pacific.”
- **N:** `inputs/02-meeting-notes.md`, “Planning notes — October 16, 14:00 Pacific.”
- **E-P:** `inputs/03-email-thread.txt`, “Field Notes decisions,” Priya, October 18, 09:00 Pacific.
- **E-A:** Same file and subject, Alex, October 18, 12:30 Pacific.
- **E-J:** Same file and subject, Jonah, October 19, 08:10 Pacific.
- **CR:** `inputs/04-approved-change.md`, “Approved change request — CR-07,” approved by Priya October 19, 16:00 Pacific.
- **Q:** `inputs/05-open-questions.txt`, “October 20, 09:30 Pacific — Mei to Priya.”

CR is the latest explicit approval and governs conflicts. E-P governs matters CR leaves unchanged; unchanged brief requirements remain. Suggestions in N are not approvals. Reported progress is not proof of subsequent completion.

## Agreed decisions and superseded directions

| Topic | Current authorized position | Evidence / supersession |
|---|---|---|
| Event | October 30 at 11:00 Pacific, 45 minutes; guest confirmed for that slot | CR; E-P; E-A. Replaces B's October 29 at 10:00. |
| Platform and accessibility | MeetRoom; captions required. Captions and capacity tests must pass October 22 before launch | E-P; N; CR. StreamHall was only Jonah's suggestion (N), not an approved switch. |
| Capacity | 80 attendees, not 120 | E-P supersedes B. Capacity test must reflect 80 (CR; E-P). |
| Commercial terms | Free registration; budget cap CAD 1,200 | B; E-P. Paid tickets were an unapproved proposal (N). No actual expenditure evidence supplied. |
| Advertising | Remains on hold until separate written campaign approval | CR strengthens N's speaker-confirmation condition. Guest confirmation (E-A) does not release spending. |
| Landing page | Jonah corrects it by October 21, 17:00; publication requires Priya's approval | CR; B. E-J reports a draft, not completed corrections; original replay promise still reported present. |
| Invitations | Mei owns drafts due October 22, 12:00 | CR refines B's email deadline. Recipient selection is unresolved (Q) and need not prevent drafting. |
| Slides and host | Alex hosts; slides due October 27, 17:00 | B retains hosting assignment; CR replaces B's October 26 slide deadline. |
| Recording/replay | No promise without written speaker consent. If absent, run live-only | CR supersedes B's automatic recording and replay-to-all instruction. E-A confirms live attendance only, not recording/replay consent. Written consent is not established in the supplied evidence. Do not record or distribute a replay based solely on the original brief. |
| Launch gates | All launch copy remains draft until platform test passes; Priya's final launch approval due October 22, 17:00; registration opens October 23, 09:00 only if required tests pass | E-P; CR; B. The opening time is conditional, not evidence of a release or permission to bypass approval. |
| Test ownership | Priya must assign the test owner by October 21, 12:00 | CR. Actual test owner is still unassigned; do not attribute testing to Jonah or Alex. |

## Proposals and unresolved issues — not approvals

1. **Test scheduling:** CR supplies a test date, not a time. Propose testing early enough October 22 to deliver results before Priya's 17:00 approval deadline. Assigned tester and Priya must confirm the slot and evidence/handoff arrangements. No pass result exists in these inputs. If tests fail or evidence/approval is missing, hold registration and escalate for remediation and a revised schedule; do not invent a fallback date. (N; E-P; CR.)
2. **Speaker consent:** Alex's October 21 task is follow-up, not a guaranteed response. Capture written scope if received; until then use live-only copy. Proposed replacement: “Join Field Notes live on October 30 at 11:00 Pacific. This is a live-only session.” This wording is a draft for Priya's review, not previously approved language. A later consent response does not automatically authorize a new replay promise or the original all-registrant distribution. Review the written scope before any such change. (E-A; E-J; CR.)
3. **Invitation audience:** All 600 newsletter subscribers versus the webinar opt-in segment remains undecided; neither list is established as authorized. Propose Priya name a consent-verification owner and decision-maker, obtain evidence and record an authorized segment before any send. Priya is coordinator, but the sources do not assign verification or sending ownership. Mei can finish draft copy independently. Do not assume speaker consent resolves mailing-list consent. (B; Q.)
4. **Operational owners/timing:** Sources do not name the registration publisher/operator or invitation sender, or set a send time. Propose Priya assign these roles and confirm dispatch timing. Target settling them by the October 22 launch review; this is a coordination proposal, not a new approved deadline. Send only after an authorized audience is established and registration is live. (B; CR; Q.)
5. **Other proposals:** StreamHall and paid tickets remain unapproved; proceed with MeetRoom and free entry. No campaign request is required to launch; leave advertising on hold unless a separate written approval is later obtained. (N; E-P; CR.)

## Execution sequence and status interpretation

The CSV is a forward plan, not a completion record. First assign the tester and resolve operational responsibilities. Alex pursues consent while Jonah fixes the page using live-only language by default; Mei drafts without selecting recipients. Schedule and execute captions/capacity testing, then obtain Priya's approval with results and corrected copy. Open registration only at the authorized time if gates pass. Invitation sending has an additional independent audience-consent gate; unresolved audience consent need not be misrepresented as a platform-test failure. Finish slides and deliver the live event under the approved consent scope. (B; N; E-P; E-A; CR; Q.)

CSV dependency IDs identify prerequisites; conditions in action/status fields remain binding. Follow-up on speaker consent can complete without consent being granted; it does not block the live-only path. Conditional advertising and recording are not treated as required launch work. Proposed assignments to Priya in coordination rows ask her to resolve gaps as coordinator, not claim she was explicitly assigned those operational tasks.

## Limits and assumptions

Only the seven supplied files were available and read, including `COMMON.md` and `PROMPT.md`. No platform, mailing system, consent record, actual draft page or spend ledger was provided or accessed. The latest known page state is E-J; no correction, test, consent response or approval completion is inferred. No new dates, roles, audience permission or campaign permission are represented as agreed. Proposed targets are explicitly labelled. This draft does not send the team email or take operational action.
