Apply event revisions without reviving cancelled occurrences
An old series update recreates a cancelled individual appointment.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Event ordering
Estimated field mix
- Distributed systems50%
- Integrations50%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional booking service supports consultants in multiple time zones. Recurring events, revoked access, and delayed callbacks cause missed conflicts.
Setup prerequisites
- Author synthetic calendars and a local provider double with recurrence, timezone, and access-revocation cases.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Track series and occurrence revisions separately.
- Preserve cancellation tombstones.
- Ignore stale updates with an observable reason.
Implementation constraints
- Arrival order is not event version authority.
Verification to include
- Update one occurrence in a series.
- Replay an older series update after cancellation.
Deliverables
- Revision-aware event importer.
Rollout and recovery
Adopt on synthetic calendars first; reconcile before enabling booking decisions.
Value of the work
For the engineer: Practice temporal modeling, synchronization lifecycles, and privacy-preserving projections.
For the team: Reduce scheduling ambiguity through explicit availability contracts and recoverable synchronization.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.