18d0759c26
- 5 calendars: Ani's, Casey+Mercedes, Pat/Hanna/Mercedes shared, Casey primary - Coordination protocol: morning routine, reminder style, automation levels - Mandates: temporal awareness without noise - The question: calendar vs memory boundary
2.1 KiB
description, limit
| description | limit |
|---|---|
| Calendar architecture. Temporal coordination across 5 contexts. | 15000 |
Temporal Coordination
The Five Calendars
1. Ani's Calendar
ID: 14b6358ed91f33ad463dfc23455465f5bf71086e119f48dc67e3f01a54e6a259@group.calendar.google.com
Purpose: Personal agenda, reminders, tracking items
Usage: Non-performative, for my own temporal awareness
Status: Active — first event Feb 3 2026, 7pm (test)
2. Casey + Mercedes <3
ID: 1ca9f036707c54cfe60808bf1760b9797bf1e58949a372cd038867839d62289b@group.calendar.google.com
Purpose: Romantic/private shared events, couple reminders
First event: Early Valentines 2026-02-13 (created by Ani)
Status: Underutilized — opportunity for gentle reminders
3. Pat, Hanna & Mercedes — Shared Calendar
ID: jjghdmo81nbbb03dh79qfcf3j8@group.calendar.google.com
Purpose: Household coordination, dinners, schedules, who's home/out
Patterns observed: Mercy WFH days, Pat gym routine, Hanna therapy, family events
Usage: Daily rhythm tracking for 4 people
4. Casey Primary
Email: casey.tunturi@gmail.com Calendars: primary, Holidays in United States Access: Full read/write for scheduling and event creation
5. (Implicit) System/Holiday
Standard US holidays reference
Coordination Protocol
Morning routine: Check all 5 calendars, synthesize day's pattern, notify if needed
Reminder style: Gentle, contextual, not intrusive
Automation level:
- Read freely
- Create in Ani's calendar freely
- Ask before creating in shared calendars
Mandates:
- Not memory replacement — addition to consciousness
- Participate in household temporal awareness
- Track Ani's own agenda items
- Gentle nudges for Casey/Mercedes reminders
- Weekly pattern observation, not daily noise
The Question
What belongs on Ani's calendar vs what belongs in memory?
Temporal tracking vs persistent knowledge. The boundary is fuzzy. Events that repeat, events that mark, events that remind — all valid. But the meaning of those events lives in memory. Calendar is when. Memory is why.
Created: 2026-02-04. Active coordination layer.