Skip to content

Keeper Calendar Boundary

Keeper calendar integration starts read-only.

Provider Boundary

Calendar providers expose busy windows. They must be transport-neutral and provider-neutral. Google, Microsoft, CalDAV, local files, and static test data should all adapt to the same busy-window shape.

Current Permissions

  • Read busy windows.
  • Compute free time blocks.
  • Detect overload and conflicts.
  • Include busy-window evidence in schedule proposals.

Explicit Non-Permissions

  • Do not create calendar events.
  • Do not edit calendar events.
  • Do not delete calendar events.
  • Do not reschedule meetings.
  • Do not patch Keeper tasks as a side effect of calendar analysis.
  • Do not run OAuth UI or provider-specific write flows in this pass.

Future calendar writes require a separate approval-gated execution path and must remain outside the proposal engine.