When services
fall out of sync.

CalAssist is a calendar and meeting assistant with team workspaces and subscription billing.

MY WORK: I implemented calendar recovery, subscription seat checks, and meeting-bot integration, with tests for the billing guard and bot configuration.
SYSTEM BEHAVIOR: Repair expired calendar state, count pending invitations before reducing seats, and let quiet meetings continue.

Visit CalAssist

CALENDAR SYNC / TEAM SEATS / MEETING BOTS

01/ 03

Repair the failed sync before retrying.

A calendar can be correct in Google and stale in the product. Recovery depends on which piece of state failed.

GOOGLE CALENDAR

10:30

Design reviewcalendar A / event 17Time changed

Update waiting

CALASSIST

10:00

Design reviewcalendar A / event 17Update pending

ONE LOCAL RECORD

Design review moves from 10:00 to 10:30 in Google Calendar.

Illustrative sequence · no calendar connection

IN CALASSIST

CalAssist refreshes rejected access, but discards an expired sync cursor—the marker of changes already fetched. It then requests a fresh window of events. Returned events update the existing local records.

Repair the state that failed before repeating the request.

One product.
Several systems to keep consistent.

Repair the failed sync before retrying.

UNDERNEATHWhy access and sync state need different repairs