Hotel booking and operations¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
| Vertical | Hospitality |
| Prototype reference | Hospitality prototype (ConnectSoft.DesignPrototypes) |
| Managed edition | Managed (D33, D34) |
| Data residency | tenant-region (D31) |
| Catalog | Examples catalog · Vision-to-Production path for this vertical |
Business problem¶
A hotel group's bookings, front desk and housekeeping do not share state; overbookings and idle rooms are common.
Product intent¶
Reservations, rates, front desk, housekeeping and guest communication as one multi-property product with a guest app.
What the Factory makes different here: the running example of the UX and Service Blueprint pages: check-in journey, state families, RTL back office.
Vision-to-Production path for this vertical¶
| Step | Factory platform | Agents | Blueprints |
|---|---|---|---|
| Vision and product plan | Agent Mesh, Control plane | Vision Architect Agent, Product Manager Agent | vision, agentic-saas-product |
| Architecture and domain | Template & Library (BC-02) | Enterprise Architect Agent | service, module, database, api-gateway |
| Experience | Template & Library, Factory Studio UX track | UX Designer Agent, Frontend Developer Agent | ux, frontend, mobile |
| Recipe and generation | Template & Library (BC-15), Agent Mesh, Tools & MCP | Vision Architect Agent, Product Manager Agent, UX Designer Agent, Backend Developer Agent, Frontend Developer Agent, Mobile Developer Agent, QA Agent, DevOps Agent | module plan from the context map |
| Quality | Observability (BC-22), DevOps / GitOps | QA Agent | test, pipeline |
| Delivery and provisioning | DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) | DevOps Agent, Infrastructure Architect Agent | infrastructure |
| Operations | Product Fleet Operations (BC-35..37) | — | handover, objectives, rollouts, incidents, off-boarding |
Delivery workflows exercised: vision-and-product-planning-workflows, research-and-ux-ui-design-workflows, software-engineering-workflows.
Generated product shape¶
C4Context
title Hotel booking and operations system context
Person(user, "Users", "Hospitality users and operators")
System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
System_Boundary(product, "Hotel booking and operations") {
System(ctx_Reservations, "Reservations", "availability, bookings, rates")
System(ctx_FrontDesk, "FrontDesk", "arrivals, check-in, folios")
System(ctx_Housekeeping, "Housekeeping", "room status, tasks")
System(ctx_Guests, "Guests", "profiles, preferences, messages")
}
Rel(user, ctx_Reservations, "uses through the product gateway GW-07")
Rel(factory, ctx_Reservations, "descriptor, health, rollouts, incidents, off-boarding")
Bounded contexts¶
| Context | Responsibility | Published events |
|---|---|---|
| Reservations | availability, bookings, rates | ReservationConfirmed |
| FrontDesk | arrivals, check-in, folios | GuestCheckedIn |
| Housekeeping | room status, tasks | RoomReady |
| Guests | profiles, preferences, messages | MessageSent |
Modules and templates¶
| Module | Template | Notes |
|---|---|---|
| Microservice ×4 | connectsoft-microservice |
|
| API gateway | connectsoft-apigateway |
|
| Back-office shell | connectsoft-blazor-saas-shell |
|
| Guest app | connectsoft-maui-base |
|
| Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product. |
Prototype reference¶
Hospitality prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.
Operations as a managed product¶
Managed; the worked example of the fleet rollout and off-boarding flows.