The booking engine manages reservations for every amenity the building offers — gym slots, coworking desks, screening rooms, rooftop bookings, guest suites, EV charger stalls. It is a single capacity model shared across the building, not a collection of per-amenity sign-up sheets.

Capacity model. Each amenity declares its capacity profile: total slots, slot duration, lead time, advance window, deposit requirements, eligibility rules. The engine tracks live availability and prevents double-booking through transactional reservation writes.

Rule evaluation. Every booking request runs through the rules engine before the slot is held. Quiet hours, capacity limits, eligibility (resident vs. guest), advance window, and deposit clearance are checked declaratively. Rules are versioned with the behavioral specification — most rule changes do not require a code release.

Lifecycle. Hold → confirm → check-in → release. The check-in step is opportunistic: it accepts an access event from the orchestration engine, a staff acknowledgement, or a resident-confirmed arrival. Unclaimed slots release automatically after a grace period, returning capacity to the pool.

Why not the PMS. Property management systems treat amenities as line items on a charge ledger. They do not model rolling capacity, contextual eligibility, or behavioral rules. The booking engine wraps the PMS for billing handoff while owning the resident-facing experience and the operational logic.

For the resident, the experience is one app, one place to book everything in the building, with consistent rules and reliable confirmations.