A common pattern
A hosted scheduler often asks for calendar access so it can compare everyone’s availability in one place.
All use cases
Kraton / Personal scheduling / source-backed demo
Find time without handing over your calendar.
A small scheduling function can solve the repetitive part of finding a time. You decide what availability goes in; the demo returns candidate slots without connecting to a calendar service.
The trade-off
Keep the task. Narrow the handover.
This Kraton demo
The typed-scheduler demo receives a time window and busy intervals as ordinary input. It has no ambient calendar access, network, or system clock.
What is actually bounded
The boundary is part of the tool.
The example is useful because it makes the allowed inputs and actions explicit—not because it claims to solve every version of this task.
- The component does not read a calendar; its caller supplies the intervals.
- No network, system clock, or randomness is available to this pure function.
- The result is deterministic for the same input and scheduling rules.
Where this example stops
This demo computes availability; it does not sync calendars, invite attendees, or book an event.
One scenario at a time