Abhishek Saxena

Property Management System / Front Desk · Documentation

Architecture

Property Management System / Front Desk's pipeline, its owned data, the events it emits/consumes, and what is out of scope.

← Property Management System / Front Desk

Board + room board + folio

Three surfaces over the shared store: the front-desk board (arrivals/departures/in-house filtered from all cockpit bookings for a date, cancelled excluded), the room-status board (deterministic physical rooms per property with scoped status overrides), and the folio (room + incidental lines, 12% tax, open→settled). The room suggestion is a deterministic next-available pick. No model pipeline, no cost_ledger write.

Owned data + shared-core reads

Reads shared booking / property / room_type. Writes its own C4 overlay — check-in records, room-status overrides, and folios — held per credential in the C4Store scope; in Stage-2 these map to demo_eco_* checkin / room / folio tables via C4Sinks, the in-memory write still driving instant UX. The data invariant holds: owner writes canonical; a viewer's check-ins, room overrides and folios are credential-scoped, ephemeral, reset-clearing.

Events + metered AI

Emits guest.checked_in (check-in), folio.posted (each charge) and guest.checked_out (settle) on the spine, consumed by #07 / #14 / #12 in later clusters. Metered AI: none — the 'AI-assist' room suggestion is a deterministic pick labelled simulated, and there is no cost_ledger write. Honesty is inspector-only (plus the on-surface simulated folio note).

Out of scope (simulated + labelled)

No real payment for folio charges or check-out settlement, no real room-lock/keycard integration, and no model-driven room optimisation. No real imagery, no PII, no proprietary metrics appear anywhere.

Architecture · Property Management System / Front Desk · Abhishek Saxena