Calendar Source Adapter
Calendar capture is an account-scoped adapter owned by
source.absorb, not an independent knowledge-writing workflow.
Current State
calendar-sync is a paused Automation V2 definition. Reactivation requires the
exact Google Calendar read-only OAuth scope, root dependencies, and a healthy
Daily Brief. The collector writes private evidence under
raw/calendar/accounts/<account>/<year>/<date>.md; legacy merged daily files
remain preserved as earlier evidence.
Route
npm run sync:calendar
npm run brain -- workflow plan source.absorb source:calendar.archive
The first command captures source revisions. The second creates an immutable review plan. Neither grants person/project/wiki mutation authority.
Completion Proof
- every requested account and API chunk completed;
- output names the account and date window;
- partial chunks retain artifacts but do not advance global freshness;
- source review binds exact revisions to stable owners;
- any proposed owner diff appears once in Daily Brief.
Repeated attendees, travel holds, and recurring meetings are routing clues, not automatic page-creation rules. A durable decision or project change may be proposed only after interrogation against the current owner.
Timeline
- 2026-08-12 | Recast the legacy direct-enrichment runbook as an
account-scoped source adapter under
source.absorb; separated exact OAuth, capture, review, proposal, and freshness authority. Source:automations/calendar-sync.md;scripts/sync-calendar.ts - 2026-05-31 | Original calendar sync page created. Source:
automations/calendar-sync.md