Alexander Mecca.
Project directory

04Personal Products and Experiments

Work Calendar Bridge

Actual product · Motion walkthrough

Keeps a work calendar usable in a separate planning calendar without relying on the destination provider’s slow subscribed-calendar polling. The bridge reads an Outlook-published ICS feed, applies field and attendee policy, previews creates, updates, and removals, writes normal events to a dedicated Google Calendar, and retains source-to-destination mapping, freshness, repair, and change evidence.

CalendarPrivacyReconciliationOperations

The calendar boundary

Read Outlook ICS. Apply the boundary. Preview the delta. Reconcile normal Google events with evidence.

  1. 01

    Readiness

    Source and destination health are checked before any event is considered for movement.

  2. 02

    Shape

    Field and attendee policy defines what the destination event receives instead of treating the source feed as an opaque subscription.

  3. 03

    Preview

    A dry-run diff makes creates, updates, removals, and unchanged events visible before any Google Calendar write.

  4. 04

    Reconcile + Repair

    Source-instance mapping updates events without duplicates; freshness, repair, rebuild safeguards, and a change ledger preserve what the bridge observed and changed.

Actual Work Calendar Bridge interface · Public-safe fixture responses · No calendar read or write performed

What the accomplishment is

The implemented capability—not a substitute illustration.

Keeps a work calendar usable in a separate planning calendar without relying on the destination provider’s slow subscribed-calendar polling. The bridge reads an Outlook-published ICS feed, applies field and attendee policy, previews creates, updates, and removals, writes normal events to a dedicated Google Calendar, and retains source-to-destination mapping, freshness, repair, and change evidence.