CALENDAR

CALENDAR

CALENDAR extracts governed intelligence from external sources.

Purpose

CALENDAR is the time axis. Every meeting governed. Every participant resolved to INTEL.

CALENDAR reads the Apple Calendar database, resolves participants to governed contacts, and builds the timeline that connects every other channel. Meetings are the anchor — iMessage, WhatsApp, Email, LinkedIn all orbit around calendar events. Read-only on source data. SHOP-safe summaries only — raw calendar stays private.

Structure

Leaf service scope. No child domains.

Required closure artifacts per scope: CANON.md, README.md, CALENDAR.md, VOCAB.md, ROADMAP.md, COVERAGE.md, LEARNING.md.

Learning lane per governed scope: LEARNING.md at the scope root is terminal and SHALL NOT nest further LEARNING/.

Source

Component Detail
Database ~/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb
Access Full Disk Access required
Tables CalendarItem, Participant, Location
Fields summary, start_date, end_date, location
Participant fields email, phone_number, is_self, status, role
Location join CalendarItem.location_id → Location.title

Unified Correspondence Timeline

Channel Join Key Coverage
CALENDAR participant.email Meeting context
EMAIL sender address Pre/post meeting correspondence
IMESSAGE phone handle Informal coordination
WHATSAPP phone JID Group coordination
LINKEDIN profile name Professional context

CALENDAR is the time axis. All other channels provide content around calendar events.

Routes

web_docs: https://hadleylab-canonic.github.io/
web_surface: https://hadleylab-canonic.github.io/SERVICES/CALENDAR/
magic:    magic://hadleylab-canonic.github.io/SERVICES/CALENDAR/

Pipeline

~/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb
  -> CalendarItem query (summary, start_date, end_date, location)
  -> Participant resolution (email -> INTEL contact)
  -> INTEL update (INTEL/{contact}.md — calendar section)
  -> LEDGER (meeting history, upcoming, cross-axiom proof)

Ecosystem Connectivity

  1. Upstream: SHOP governance and SERVICES meta-governance.
  2. Runtime: SHOP-safe outputs only. Raw calendar stays private (auth-gated).
  3. Source: ~/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb — read-only, Full Disk Access required.
  4. Sink: INTEL/*.md — calendar ledger updates.
  5. Cross-service: IMESSAGE + CALENDAR + EMAIL = unified correspondence timeline.
  6. Participant schema: email, phone_number, is_self, status, role.
  7. Location schema: Location.title joined via CalendarItem.location_id.

Pages

Page Sections
Overview Purpose, Structure
Pipeline Pipeline, Ecosystem Connectivity
Ecosystem Routes

Default: Overview.

*CALENDAR SPEC SERVICES*
TALK AUTO