Group & Corporate / MICE Bookings · Documentation
Architecture
Group & Corporate / MICE Bookings's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Group & Corporate / MICE BookingsPipeline — RFP, quote, confirm
The flow is RFP (seeded, status overlay) → quote build (room subtotal = BAR × rooms × nights × (1 − negotiated%) + event-space day rate × nights + 12% tax + narrative) → send (simulated email) → confirm (group booking + invoice + optional corporate account) or decline. The quote draft is a deterministic template composer — no model call.
Events + metered AI
Emits quote.sent (send), group.booked + booking.created (confirm) and corporate.created (new company); uses the host notification for the simulated quote email (the #34/#35 send path). Metered AI: none — the rfp-read→quote-draft stage records a $0 cost_ledger row labelled 'deterministic (rules · $0)'; there is no demo_cache. Honesty is inspector-only (plus the on-surface AI-assist-draft/simulated badge).
Out of scope (simulated + labelled)
No real quote-drafting LLM, no real email delivery (the quote lands in the in-app sent viewer), and no real invoicing/payment rail — settlement belongs to the simulated Payments & Partner Settlements #34 in a later cluster. No real imagery, no PII, no proprietary metrics appear anywhere.