A commercial platform, not a collection of screens.

Every major workspace is backed by domain services, API contracts, role boundaries, smoke flows and synthetic demo evidence.

Every major workspace is backed by domain services, API contracts, role boundaries, smoke flows and synthetic demo evidence.

Checkout, stayover, maintenance and inspection tasks feed a readiness state machine before front desk can check guests in.

Arrivals, departures, no-shows, room moves, deposits, documents, messages and dirty-room overrides stay visible and auditable.

Beds, rooms, buildings, floors, room types, dorm restrictions, accessibility constraints and blocked inventory are tenant scoped.

Work orders block availability, restore readiness after verification and keep operational downtime visible to managers.

Guest token lookup, stay overview, pre-check-in, messages, house rules, requests and privacy-safe workflows are modeled locally.

Mock ledger, folios, deposits, refunds, POS revenue, tax summaries and daily close warnings behave like internal hotel controls.

Room readiness is the selling wedge.

The workflow prevents avoidable reception failures by turning cleaning, inspection and maintenance into a hard operational signal.

Checkout or stayover creates the right task

Housekeeper starts, pauses, reports issues and records lost-found

Supervisor approves, rejects or escalates to maintenance

Front desk check-in unlocks only when the room or bed is ready

The public site shows the same operational model as the repository: readiness, API depth, i18n, audit boundaries and realistic SaaS controls.

ready_for_checkin

Room/bed can accept arrival

front desk

inspection_required

Supervisor approval needed

housekeeping

out_of_order

Availability blocked by maintenance

maintenance

override_audited

Permissioned exception with reason

manager