Project busy intervals without exposing event descriptions
Availability responses leak private appointment titles to bookers.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Privacy · API projections
Estimated field mix
- Privacy engineering60%
- API design40%
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
- Expose only necessary busy intervals.
- Scope calendars by current access grants.
- Exclude titles, attendees, and notes from public projections.
Implementation constraints
- Private provider fields remain outside scheduling responses.
Verification to include
- Compute availability from authorized events.
- Seed sensitive markers and verify they never appear in outputs.
Deliverables
- Privacy-preserving availability projection.
Rollout and recovery
Replace detailed projections before public availability is enabled.
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.