Business Problem & Solution

A booking is a promise; the front desk is where it becomes a physical stay. Someone has to see the day's arrivals, departures and in-house guests, assign a real room at check-in, open and grow a folio of charges, and settle it at check-out. Without one surface for this, the rest of the platform is blind to what's actually happening on property — which rooms are occupied, who has arrived, what's owed.

The Property Management System / Front Desk runs that desk on the shared booking record. It turns upcoming bookings into in-house stays, manages the physical room board, and is the origin of the stay events the rest of the ecosystem listens for.

It proves the on-property layer is wired to the same truth as everything else: the arrivals board is built from all cockpit bookings (direct, channel and group), a check-in here shows up on the cockpit #20 timeline, and the stay events it emits are what later clusters (service #07, housekeeping #14, loyalty #12) consume. The room board, folio and check-out flow are live against synthetic data.

It simplifies the money and the 'AI'. Folio charges and check-out settlement are a simulated ledger — no real payment is taken, and the surface says so. The room suggestion is labelled 'AI-assist' but is a deterministic next-available pick, not a metered model call. The Architecture doc is explicit about both.

Synthetic only — physical room inventory is derived deterministically per property (fixed-seed status mix: available / occupied / dirty / out-of-service), and folios accumulate synthetic charge lines with a representative 12% tax. Figures are representative and labelled; no real brands, customers, or PII.