Cadence
Calendars, availability, reminders, and recurrence as a shared service — the scheduling layer the work engines deliberately don’t own.
In the constellation
Cadence highlighted in the live map — hover or tap any node to explore.
Why it exists
Calendars, availability, reminders, recurrence — every app that schedules anything needs them, and almost every app bolts on its own half-built version. Time-zone math, DST edge cases, and recurring-event expansion are quietly some of the easiest things to get wrong.
The work engines deliberately stop at the clock: they manage what gets done, not when. That leaves a real gap with nothing in it.
What Cadence is
Cadence is the shared time layer. It answers “when is everyone free,” expands recurring events correctly across time zones, and fires reminders at exactly the right moment — so no app has to reinvent the calendar.
It does the clock, not the calling. The engine computes availability and fires timers; deciding what’s the right time and what matters most stays with the app above it.
What it does
Availability & scheduling
Free-busy and multi-party scheduling computed across calendars, correctly.
Recurrence
Recurring events expanded with full time-zone and DST handling — the part everyone gets wrong.
Reminders & timers
Deterministic reminder firing at a specified time — “fire this at T,” reliably.
Time-reasoning
Answers “when is free,” “when is next,” and “what’s overdue” across people and commitments.
The line between judgment and machinery
AccelMars draws one hard line through every product: what an AI decides, and what runs deterministically. Cadence sits on the deterministic side.
Deterministic by design
- ▪ Calendar and availability math
- ▪ Recurrence expansion with time-zone correctness
- ▪ Reminder and timer firing
Cadence does the clock, not the calling. It computes when things can happen and fires events on time; what’s the right time and how to prioritize is the app’s judgment, above the engine.
How it connects
Planned — designed, not yet built. It will power scheduling in Aide, operational timing in Ops, and follow-up reminders across future support apps.
Open-core, like Anchor and Booster — the mechanical engine in the open.