Cadence /

The problem worth solving.

A time slot can look available in two windows at once. One person begins a reservation while another confirms an overlapping appointment, or an abandoned checkout appears to occupy the schedule indefinitely. Local time adds another complication: a clock transition can make apparently valid start and end times cross an interval when the resource is closed.

Cadence models a reservation as a lifecycle. A resource has explicit working hours and timezone. A temporary hold protects a candidate interval for a limited period; an operator confirmation creates the booking. Cancellation and expiration release capacity according to server-side rules, so the schedule does not depend on whether somebody left a browser tab open. Conflicting actions receive an explicit result rather than two contradictory confirmations.

This independent Lumia application focuses on capacity-one resources such as a room, an individual appointment calendar or a dedicated service station. Its acceptance fixtures exercised simultaneous holds, exact interval boundaries and a repeated daylight-saving hour. They demonstrate behavior under those controlled conditions, not customer bookings, payment collection or a guarantee of universal scheduling correctness. The intended benefit is an understandable record of who has reserved which resource and whether that reservation is still valid.

Designed for: Appointment and facility operators reserving one room, person or service station per resource, with operator confirmation and explicit local working hours.

From input to a useful result.

What the software actually did.

These results come from internal workflow testing of the local product. The records are controlled test inputs; customer deployments and commercial impact have not been measured.

Make the boundary clear.

• Each resource supports capacity one; group inventory, pooled capacity and multi-resource atomic booking need a different model.
• Reservations are future, whole-minute intervals of at most 12 hours and must remain within a supported local working day.
• The tested confirmation is operator-managed with payment not required. It does not represent a paid reservation or a payment authorization.
• ICS export is a downloadable record, not verified email delivery or two-way synchronization with Google or Microsoft calendars.
• The daylight-saving test covers a specific New York fall-back boundary. Spring-forward and broader timezone coverage remain separate acceptance work.

Questions before you start.