Calendar and elapsed-time contracts
All units, original anchors, month ends/leap years, DST, inclusive windows, nextOnOrAfter and strict cutoff boundaries.
Scheduling / INTERACTIVE WORKSHOP
Cadence v1.0.0Explore anchored dates and deadlines
Preview anchor-derived dates or request an inclusive bounded window. Inspect strict cutoffs at a selected clock and see that host skip flags never move the anchor.
01 / CONFIGURE
Choose a scenario. Change the inputs or build a sequence of commands.
02 / RUN
Execute the installed package against a new fictional example.
03 / INSPECT
Follow the result, actual calls, generated output and integration code.
THE WORKBENCH
Make it your example.
Your server-side changes are temporary. External-service examples use local response fixtures. Start with sample data.
Start with a preset, or change the input and run it.
The behavior is the example.
Your result will show the values, decisions and generated output from the actual package.
Calls used by this scenario. The handbook explains setup, authorizers, storage and error recovery.
The complete response is shown as data. Wide PHP integers are transported as exact decimal strings. Values are never evaluated as PHP or JavaScript.
Run an example to inspect its response.
The last two successful run states stay in this tab’s memory. Run a changed example to compare the actual package results.
What you can exercise here.
Resource-limit failure
A window that exceeds the selected limit returns a package failure rather than partial dates.
Scheduling workflows
Persisted anchors, holidays, jobs, notifications, capacity and billing remain host responsibilities.
UNDERSTAND THE BEHAVIOR
Every occurrence derives from the original anchor.
Explore recurrence, inclusive windows and strict elapsed-hour deadlines. Change the timezone, resume point and display skips while retaining the original schedule.
Short months do not cause permanent drift
Schedule::at derives each occurrence from the anchor. A January 31 schedule can clamp February and return to March 31. nextOnOrAfter resumes from a date without replacing that anchor.
A window is complete or rejected
Window mode calls between with inclusive endpoints and the selected count as a resource limit. If the complete window contains too many occurrences, the package refuses it instead of silently returning a truncated schedule.
Cutoffs use elapsed time and strict comparison
Cutoff::at subtracts actual hours, which can cross a daylight-saving offset change. The response checks one second before, exactly at, and one second after the cutoff. Exact deadline is closed.
Skipping is a host display decision
skip_indices hides selected returned positions from host_visible_occurrences. The complete occurrences remain present, and future package dates still derive from the same anchor. The workshop does not schedule jobs or persist cancellations.
GO FURTHER
Try the boundary cases.
Watch month-end and leap-day recovery
Run the default monthly schedule, then Leap-day recovery. Expected: January 31 clamps to February 29 in 2028 and returns to March 31; yearly February 29 clamps in non-leap years and recovers in the next leap year. Increase count to inspect the return.
Compare DST with a fixed-offset zone
Run DST cutoff and inspect occurrence offsets, cutoff and elapsed_seconds. Expected: a 24-hour cutoff is 86,400 seconds even across a local-clock change. Repeat with America/Phoenix and compare wall-clock times.
Prove inclusive and bounded windows
Run Inclusive same-instant window, then Refuse truncation. Expected: an occurrence exactly on both endpoints is included once; an insufficient limit returns a rejection and no partial occurrence list. Increase count to admit the complete window.
Resume and skip without drifting
Run Resume the original schedule, then Skip a displayed delivery. Expected: the resume point selects a future anchor-derived occurrence, and hiding one displayed position changes only host_visible_occurrences. Compare the remaining complete dates before and after the skip.
COMPOSE THE RESPONSIBILITIESUseful alone.
Useful alone.
Better when the boundaries fit.
Cadence calculates dates and deadlines. Flow or Workflow can use those dates in domain decisions; queues, job ownership, delivery retries and cancellation records remain application responsibilities.