---
type: calendar-spec
status: deferred
phase: 2
created: 2026-06-15
---

# Calendar (phase 2)

**Status: DEFERRED.** Build after the vault is operational and you've run a full monthly cycle.

## Goal (per user)

> create some calendar that syncs across devices with notifications and that automatically adds events and reminders for any announcements outlined in the Process.pdf

## Source spec (from Process.pdf)

**Tier 1 events (always previewed + reviewed):**
FOMC, US CPI, NFP, ECB, SNB, BoJ.

**Tier 2 events (commented in weekly note):**
ISM/PMIs, retail sales, PCE, Eurozone HICP, China credit/PMI, refunding announcements.

**Weekly structural data:**
CFTC COT (Friday release), CTA positioning estimates, ETF flows for gold.

## Open design decisions (need user input)

1. **Calendar backend** — Google Calendar (most likely, given cross-device + notification), iCloud, Outlook, or Telegram-only reminders? Affects everything downstream.
2. **Auto-add source** — pre-populated 12-month ICS (one-shot), or scrape on schedule (maintained by `scripts/calendar_sync.py`)?
3. **Reminder windows** — what's the lead time? T-24h + T-1h is standard for Tier 1; Tier 2 probably T-1h only.
4. **Notification channel** — Telegram (already wired) + native calendar notification, or just one?

## Architecture (proposed)

```
scripts/calendar_sync.py
  inputs:
    - events.yaml (Tier 1/2 with date rules)
    - holiday calendar (US/EU/CH/JP/CN)
  outputs:
    - .ics file (or direct Google Calendar API push)
    - per-event reminders
  schedule:
    - daily 06:00 cron — refresh next 90 days
  notifications:
    - native calendar
    - Telegram push at T-24h and T-1h for Tier 1
```

## Open file location for events

Likely `07-calendar/events.yaml` once spec is finalised.

## See also

- [[RECOMMENDATIONS]] — full architecture, source mapping, cost analysis
- [[../00-methodology/process#3. Data and event coverage]]
- [[../TODO#H. Calendar (phase 2)]]