The booking flow runs every time a resident reserves an amenity — a gym slot, a coworking desk, a screening room, a rooftop reservation, a guest suite, an EV charger stall. The same flow handles every amenity in the building because the underlying behavior is the same: declare a window, evaluate eligibility, hold capacity, confirm, check in, release.

A resident initiates a request from the resident app. The booking engine evaluates the request against the rules engine — quiet hours, capacity, eligibility, advance window, deposit clearance — and either holds the slot, suggests an alternative, or denies the request with a clear reason. The hold is transactional: capacity does not double-book even under contention.

Confirmation is acknowledged through the resident's preferred channel and persisted in the operating layer's record. At check-in, the booking engine accepts evidence of arrival from the access orchestration engine, a staff acknowledgement, or a resident-confirmed arrival. Unclaimed slots release automatically after a grace period, returning capacity to the pool. Every step is logged against the behavioral specification, so cell-level scoring can determine whether the booking experience is meeting the standard.