Task library BCALENDAR Integrations · Phased project Calendar availability synchronization A fictional booking service supports consultants in multiple time zones. Recurring events, revoked access, and delayed callbacks cause missed conflicts.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 28h + setup
Suggested stack TypeScript · iCalendar · HTTP Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BCALENDAR-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice temporal modeling, synchronization lifecycles, and privacy-preserving projections.
What the team gains Reduce scheduling ambiguity through explicit availability contracts and recoverable synchronization.
Before you start Author synthetic calendars and a local provider double with recurrence, timezone, and access-revocation cases. Delivery agreement Deliver local availability calculations and sync behavior; send no invitations or calendar writes externally.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Model instants, zones, and recurrence.
PHASE 2 Handle event updates and provider failures.
PHASE 3 Verify privacy, cutover, and recovery.
Define temporal semantics Model instants, zones, and recurrence.
BCALENDAR-101 Entry ticket; project setup still required Estimated field mix
Integrations 60% Backend 40% BCALENDAR-102 Depends on BCALENDAR-101 Estimated field mix
Backend 60% Integrations 40% BCALENDAR-103 Depends on BCALENDAR-102 Estimated field mix
Integrations 40% Performance engineering 40% Backend 20% Synchronize availability Handle event updates and provider failures.
BCALENDAR-104 Depends on BCALENDAR-103 Estimated field mix
Distributed systems 50% Integrations 50% BCALENDAR-105 Depends on BCALENDAR-104 Estimated field mix
Integrations 60% Site reliability 40% BCALENDAR-106 Depends on BCALENDAR-104 Estimated field mix
Privacy engineering 60% API design 40% BCALENDAR-107 Depends on BCALENDAR-105, BCALENDAR-106 Estimated field mix
Security 50% Privacy engineering 30% Integrations 20% Rehearse edge cases Verify privacy, cutover, and recovery.
BCALENDAR-108 Depends on BCALENDAR-106, BCALENDAR-107 Estimated field mix
Database engineering 40% Integrations 30% Distributed systems 30% BCALENDAR-109 Depends on BCALENDAR-105, BCALENDAR-108 Estimated field mix
System design 40% Integrations 30% Site reliability 30% BCALENDAR-110 Depends on BCALENDAR-109 Estimated field mix
Site reliability 60% Integrations 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.