# Field Notes — decision log and coordination plan

**As of October 20, 2026, 10:00 Pacific. Draft only; no project messages sent or operational actions executed by the preparer.** All dates below are 2026 and all times Pacific. The supplied packet is the sole evidence base. Action statuses describe that evidence, not independently verified project activity.

## Source register

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

`COMMON.md` (Shared assignment instructions) and `PROMPT.md` (Task 4 — Turn conflicting project documents into an action plan) govern deliverables and the as-of time, not project approvals. All seven supplied files were read.

## Agreed decisions and supersession

Explicit approvals control their subject matter; later suggestions do not override approvals. Unchanged original requirements remain in force. S4 is the latest explicit approval, but is not evidence that its actions have been completed.

| Topic | Controlling decision | Earlier instruction or proposal resolved | Evidence |
|---|---|---|---|
| Event schedule | October 30 at 11:00; 45 minutes. Guest attendance confirmed for this slot. | October 29 at 10:00 is superseded. The guest confirmation concerns live attendance, not recording. | S1 → S3-P, S3-A; S4 makes date/time final. |
| Platform and capacity | MeetRoom; maximum 80 attendees. | StreamHall was only suggested; no switch approved. Original 120-seat cap is superseded. | S1, S2 → S3-P. |
| Price and budget | Free registration; CAD 1,200 cap. | Paid tickets were proposed, never approved; later approval retains free entry. No evidence of actual expenditure is supplied. | S1, S2, S3-P. |
| Launch gates | Captions required. Captions and capacity tests must pass October 22 for registration to open October 23 at 09:00. All launch copy stays draft until the platform test passes; Priya's final launch approval is due October 22 at 17:00. | No unconditional publication or send authorization. Passing tests does not replace Priya's approval. | S1, S2, S3-P, S4. |
| Test accountability | Priya must assign a test owner by October 21 at 12:00. | No test owner has been named in the supplied record. | S4. |
| Landing page | Jonah owns corrections due October 21 at 17:00. | Original October 21 deadline is made precise. His October 19 statement that he could update the page is not evidence of completed corrections; the reported draft still had a replay promise. | S1, S3-J, S4. |
| Invitations | Mei owns invitations due October 22 at 12:00. | Original October 22 email deadline is made precise. This is a draft deliverable, not an approved send time or audience. | S1, S3-P, S4, S5. |
| Slides and hosting | Alex remains host; slides due October 27 at 17:00. | Original October 26 slide deadline is superseded. | S1, S4. |
| Recording and replay | No recording or replay promise without written speaker consent; absent consent, run live-only. Alex's consent follow-up is due October 21, time unspecified. | Original instruction to record and email replay to all registrants is no longer unconditional. Only live attendance consent is evidenced. A request deadline is not a deadline by which the speaker must grant consent. | S1 → S3-A, S4. |
| Paid advertising | Remains on hold pending separate written campaign approval. | The October 16 speaker-confirmation prerequisite alone cannot release spending, even though the speaker has now confirmed. | S2, S3-A → S4. |
| Project coordination | Priya coordinates and approves landing publication/final launch. | No supplied approval assigns her every unresolved operational task or designates the campaign approval authority. | S1, S4. |

## Unresolved matters and proposed handling

These are recommendations or open issues, **not additional approved decisions**. Proposed assignments and times in `action-plan.csv` are explicitly labeled. The dependencies column contains human-readable conditions and coordination notes, not a machine-executable dependency graph; a referenced action may be explicitly identified as unnecessary for a particular step.

1. **Platform ownership and test timing (A01–A02, A09–A10).** Owner is explicitly unassigned. October 22 testing has no exact hour, but approval is due at 17:00. Recommend scheduling tests and a results review before that deadline, with retest time if feasible. Priya should confirm the timetable with the newly assigned owner; do not invent a booked test slot. No test results or launch approval are supplied. [S4]
2. **Replacement copy (A03–A05).** Jonah requested language; no approved replacement appears. Proposed draft: “Join Field Notes live on October 30 at 11:00 Pacific. Free registration; limited to 80 attendees.” Remove the old replay promise now rather than waiting for consent. Priya is the proposed wording reviewer because she owns publication approval; this interim review deadline is a recommendation. Review proposed wording during drafting rather than requiring Jonah to finish corrections before review starts at the same deadline. Default to live-only while consent is absent. If written consent arrives, check that it explicitly covers the intended recording and replay use before proposing revised copy; the original brief specifies replay to all registrants, but that instruction is now conditional on appropriate written consent. Do not assume a narrower consent permits all of the original uses. Replay production ownership and send timing are not specified; clarify them if consent makes replay feasible. [S1, S3-A, S3-J, S4]
3. **Invitation consent and audience (A06–A08, A13).** Neither all 600 newsletter subscribers nor the webinar opt-in segment is approved by the packet. Consent records are not supplied, and Mei cannot verify scope from this file. Recommend Priya coordinate assignment of a verification/decision owner; that assignment is not yet agreed. Mei can finish draft copy without selecting recipients. Recommend holding invitation sending until a permitted audience is documented; this is a proposed safeguard, not a newly evidenced project approval. Missing evidence in this packet does not establish that either segment lacks consent elsewhere. Speaker consent and recipient consent are separate issues. [S5; S4 for draft deadline]
4. **Release ownership and schedule (A11–A13).** Draft ownership does not prove who publishes registration or sends invitations. Those operational owners and invitation send time are not specified. Recommend resolving them by the launch review and sending only once registration is live. Naming a publisher or sender, and planning a provisional send time, can proceed before audience verification; actual sending must await that decision under the proposed safeguard. MeetRoom is the approved event platform, but the registration system is not identified in the packet. Audience uncertainty should hold invitations; it is not a stated prerequisite for registration publication. Registration remains subject to the approved platform tests and Priya's approval. [S1, S3-P, S4, S5; recommendations explicitly added here]
5. **Failure contingency (A14).** If tests fail, do not pass on October 22, or cannot support timely approval, do not assume October 23 registration can open. Keep copy in draft until tests pass, keep registration unpublished without Priya's approval, and obtain Priya's direction on retest and revised launch timing. No alternative launch date is approved; the event date remains final unless explicitly changed. [S3-P, S4]
6. **Event operations and campaign ownership (A16–A17).** Alex is the host, but a separate platform operator is not identified; do not assume the test owner also operates the event. Campaign owner, campaign timing and separate written approval authority are unspecified. Paid advertising and related campaign spend remain on hold; this is not an evidenced blanket ban on unpaid planning or unrelated project spending. [S1, S2, S3-A, S4; unspecified roles reflect packet limits]

## Recommended execution sequence

- **October 20–21:** Remove the replay promise and align landing details; Alex seeks written consent in parallel. Priya assigns the test owner by October 21 noon. Propose the test/review timetable and resolve who will verify recipient permissions. Jonah completes corrections by October 21 at 17:00. Do not delay safe live-only drafts for a speaker response. [A01–A07]
- **October 22:** Mei completes invitation drafts by noon, even if recipients remain unresolved. Assigned owner runs captions and capacity tests; recommended timing is early enough for Priya's 17:00 approval review. Confirm release owners. If gates fail, escalate rather than publish automatically. [A08–A11, A14]
- **October 23:** Open registration at 09:00 only if October 22 tests passed and Priya approved. Invitation sending is separately held for verified audience, named sender and agreed timing; no send deadline is supplied. [A12–A13]
- **October 27–30:** Alex supplies slides by October 27 at 17:00 and hosts October 30 at 11:00 for 45 minutes. Plan live-only unless appropriate written consent is obtained. No replay should currently be promised or executed: appropriate written consent is not evidenced. The original replay-to-all-registrants instruction is conditional, not an unconditional authorization or a permanently canceled plan. Advertising stays on hold. [A15–A17]

## Assumptions and limits

- Date-only deadlines retain **time unspecified**; no end-of-day time has been invented. Proposed internal deadlines are not approvals.
- No missing consent, correction completion, test pass, audience decision, approval, send or spend is inferred from silence. Jonah's initial draft and the guest's live attendance confirmation are explicitly reported; subsequent corrections and consent follow-up are not reported complete. [S3-J, S3-A]
- This packet contains neither underlying mailing consent records nor a written speaker recording/replay consent document. No external systems were accessed. A live-only launch can proceed without recording consent if its other approved gates are satisfied. [S4, S5]
- The output is a coordination draft, not evidence of operational execution. Human decisions, testing, consent verification and approvals remain necessary.
