# Field Notes — decision log and coordination plan

**Snapshot:** October 20, 2026, 10:00 Pacific. Draft only; no messages sent or project actions performed. All dates below are 2026 and all times Pacific. Status describes the supplied evidence, not verified live project state.

## 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”.
- **S3P:** `inputs/03-email-thread.txt`, “Field Notes decisions”, Priya, October 18, 09:00 Pacific.
- **S3A:** same file and subject, Alex, October 18, 12:30 Pacific.
- **S3J:** 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 snapshot. Source keys in this log resolve to the filenames and records above; the CSV uses full citations.

## Agreed decisions and supersession

| Topic | Operative decision | Evidence and disposition of earlier instruction |
|---|---|---|
| Event schedule | October 30 at 11:00; 45 minutes. Expected end 11:45 is calculated, not separately approved. | S3P changes S1's October 29 at 10:00; S4 makes the new start final. S3A confirms guest availability. Duration retained by S3P. |
| Platform and attendance | MeetRoom; maximum 80 attendees. | S3P explicitly keeps MeetRoom and replaces S1's 120-person cap. S2's StreamHall suggestion was never approved. |
| Commercial terms | Free entry; budget cap CAD 1,200. | S1 and S3P. S2's paid-ticket proposal was not approved and is not operative. |
| Coordination and hosting | Priya coordinates; Alex hosts. | S1; not changed by S4. |
| Landing page | Jonah owns corrections due October 21 at 17:00. Draft exists, but corrections are not evidenced complete. | S4 specifies the deadline; S3J reports a ready draft still containing the original replay promise. Jonah's offer to update it October 19 is not proof of completion. |
| Invitations | Mei owns invitations due October 22 at 12:00. Plan treats this as draft completion under the launch-copy hold; recipient choice remains unresolved. | S4 refines S1's October 22 email deadline but does not specify a send time. S3P requires launch copy to remain draft until test pass; S5 permits drafting without recipient selection. The draft-delivery interpretation does not authorize sending. |
| Slides | Alex owns slides due October 27 at 17:00. | S4 replaces S1's October 26 deadline. |
| Launch gates | Captions and capacity tests must pass October 22; final approval is Priya's, due October 22 at 17:00. Registration opens October 23 at 09:00 conditionally. | S2 requires captions and testing before registration publication; S3P keeps all launch copy in draft until test pass; S1 requires Priya's page approval; S4 specifies tests, approval and opening. No test results or launch approval supplied. |
| Test ownership | Priya must assign a platform test owner by October 21 at 12:00. | S4 explicitly says the owner is unassigned. Do not treat Priya as the test executor. |
| Speaker consent and replay | Alex follows up by October 21. No recording/replay promise without written speaker consent; absent consent, run live-only. | S3A confirms live attendance only, not recording/replay. S4 supersedes S1's instruction to record and email replay to all registrants. Neither a request nor guest attendance confirmation is permission to record. |
| Advertising | Paid advertising remains on hold pending separate written campaign approval. | S4 supersedes the implication in S2 that guest confirmation alone could release the hold. S3A's confirmation does not authorize spending. No campaign approval supplied. |

## Unresolved issues and proposed coordination decisions

These are recommendations, not additional approvals. Proposed dates in the CSV are planning targets, not commitments from the inputs. An owner marked “proposed” has not accepted that new task; “TBD” remains unassigned.

1. **Test scheduling and failure path.** S4 gives October 22 for tests but no time, leaving a potential conflict with approval at 17:00. Ask Priya and the appointed tester to schedule an early October 22 slot, allow remediation/retest time, and provide results before approval. No exact slot, test procedure or evidence exists. If either test fails, keep copy in draft and registration closed while arranging remediation/retest. Preserve the original opening if both tests pass October 22 and approval is obtained in time; if these gates cannot be met, ask Priya to decide a revised opening/approval schedule. No fallback date is approved. The final event date remains October 30 unless explicitly changed. (S2, S3P, S4.)
2. **Noon invitation deadline versus tests.** Mei can complete drafts by noon even if testing is later that day. No dispatch deadline is explicitly supplied; this plan treats noon as draft delivery, consistent with the launch hold and S5. Proposed sequence: draft → test pass → launch approval → registration open → dispatch to a verified, approved audience. The send time and dispatcher are not assigned. An unresolved invitation audience need not prevent registration opening if the stated launch gates are met. (S3P, S4, S5; dispatch sequence is a recommendation.)
3. **Invitation consent scope.** Do not assume either all 600 newsletter subscribers or the webinar opt-in segment is authorized. S5 explicitly cannot verify scope. Recommend Priya designate an evidence verifier and recipient decision-maker; neither role is assigned in the packet. Obtain the relevant consent records and decide the eligible audience before sending. If unresolved, hold dispatch, not drafting. Speaker permission and subscriber permission are separate issues. (S5.)
4. **Speaker permission and copy.** Alex's October 21 deadline is for follow-up, not guaranteed receipt of written consent; the time of day is unspecified. Do not make Jonah's 17:00 correction deadline depend on a reply. Proposed default replacement: “Join us live on October 30 at 11:00 Pacific. This is a live-only session.” Remove the existing replay promise now as part of corrections; use live-only copy unless written permission is received and its scope supports a revised claim. Priya should review final language in launch approval. This wording is a proposal, not approved copy. Missing recording consent does not block a live-only launch/event. (S3A, S3J, S4.)
5. **Operational ownership.** Page design ownership does not prove Jonah owns publication, and invitation writing does not prove Mei owns dispatch. Recommend Priya assign both operators before launch; keep those execution owners TBD until confirmed. Alex is the existing host; recommend he confirm live-only operation, including recording disabled when consent is absent, before the event. The operational check is proposed, while the live-only rule is approved. (S1, S4, S5.)
6. **Advertising.** No need to create a paid campaign to meet this plan. Keep the hold; if advertising is desired, identify a campaign owner and obtain separate written approval within the existing budget cap before spending. Campaign owner, approval deadline and spend are not supplied. (S3P, S4.)

## Realistic next-step sequence

1. Now through October 21: Priya assigns the tester; coordinate the October 22 test slot and operator ownership. Alex seeks written consent. Jonah corrects the page using live-only language unless appropriately authorized otherwise. Start audience evidence verification without delaying Mei's draft.
2. October 22: Mei completes draft invitations by noon. Assigned tester checks captions and the 80-attendee capacity and records results. Arrange completion before Priya's 17:00 approval deadline; escalate failures or delays rather than silently moving dates.
3. October 23 at 09:00: assigned publisher opens registration only after passing tests and Priya's approval. Dispatch invitations only after audience verification/decision and registration availability, at a separately confirmed time.
4. October 27 at 17:00: Alex supplies slides. Before October 30 at 11:00, confirm consent-dependent recording settings and run the 45-minute event live-only if written consent is absent. Advertising stays held unless separately approved.

## Evidence limits and plan conventions

No platform access, consent records, written recording permission, corrected copy, test results, final approval, publication evidence, campaign approval or audience decision is supplied. Guest attendance is confirmed for the future event, not already completed; a landing draft is reported ready (S3A, S3J). No consent request, corrections, tests, approval, delivery or event execution is inferred complete from elapsed dates. Original inputs are preserved. CSV dependencies are human-readable conditions, not a machine-ready predecessor graph: references may be prerequisites, conditional triggers or explicitly nonblocking checks. Including invitation drafts in the launch review is a proposed coordination step, not a new approved registration gate. A publisher is needed for opening, but assigning a dispatcher or resolving invitation recipients is not a prerequisite to opening. A conditional consent check is not a requirement to obtain consent when live-only is available. Date-only source deadlines remain date-only with time unspecified. Proposed targets and tasks are explicitly labeled.

Review history: see `change-log.md`; the initial files are retained in `original-submission/`.
