October 1 · two management markers overlap
Launch Command (9–9:30 a.m.) overlaps Business / Finance / Risk (9–9:35 a.m.). Maya should reconcile the work sequence. These are workflow markers, not two required Founder meetings.
Source recordPublished evidence snapshot: . Source observations retain their dates.
WEDNESDAY, SEPTEMBER 23, 2026
The company calendar.
Meetings, deadlines, work rhythms and launch milestones.
Evidence through Arizona · source observations keep their own times
Decisions have dates.
Google Calendar + operating recordsCaptured Sep 19–Oct 4 · checked Sep 22, 6:11 PM Arizona
Dated snapshotTAKE THESE DATES WITH YOU
34 recorded dates in this view
Download a calendar copy of this month and these filters. Arizona times; no invitations or live sync. 2 superseded, undated or invalid records excluded.
36 in view
Company records only · read-only view · no live Google Calendar sync
Recurring work, with its actual state
Configuration and completed runs are different records.
Leadership & board preparation
Every 2 hours · active configurationPrepare the Sunday packet, then maintain evidence addenda. The exact next trigger was not available; completed runs need their own receipts.
Schedule evidenceWebsite & daily brief
Daily · intended 9 a.m. ArizonaHistorical configuration observed September 19: next trigger then recorded as September 20 at 9:01:16 a.m. Arizona. That date is not a current next run; subsequent execution must be checked against dated release receipts.
Schedule evidenceFounder coordination
Daily · 9 a.m. capacity and 4:30 p.m. reconciliationFounder September 20 direction supersedes the earlier two-hour proposal. Configured cadence is not a receipt for any later execution.
Schedule evidenceCompany decisions without dates
Undated decisions stay visible without invented calendar slots.
Name and test recovery responsibility
Fernandez · Priya · Date not assigned · before readiness sign-off
View evidence