Booking Operations Cockpit · Documentation

Architecture

Booking Operations Cockpit's pipeline, its owned data, the events it emits/consumes, and what is out of scope.

Aggregation + workflow, no model

The cockpit is an aggregation and workflow surface. It composes cockpitBookings = channel (#17) ⊕ group (#40) ⊕ direct (foundation) from the shared store, derives exceptions from booking state, and builds per-booking timelines. There is no pipeline of model stages and no cost_ledger write of its own.

Owned data + shared-core reads

Reads the shared booking table (all sources) plus the channel/group bookings and PMS check-in state held in the C4Store scope. Its only own write is resolved-exception ids (bulk actions write audit + a simulated notification). In Stage-2 resolutions map to demo_eco_* rows via C4Sinks.cockpitResolution. The data invariant holds: owner writes canonical; a viewer's resolutions are credential-scoped, ephemeral, reset-clearing.

Events + cross-links

Consumes the booking sources produced by host #01, channel #17, PMS #30 and group #40; emits notification.sent on bulk/notify. Navigational cross-links point to PMS #30 (live), Fraud #18 and Refund & Dispute #21 (planned in later clusters). It feeds analytics #24 (C8). No metered AI; honesty is inspector-only on this surface.

Out of scope (simulated + labelled)

No real payment capture (timeline payment lines are simulated), no real outbound messaging (bulk sends land in the #35 sent viewer), and no live fraud/refund decisioning (cross-links are navigational to later-cluster apps). No real imagery, no PII, no proprietary metrics appear anywhere.

Architecture

Aggregation + workflow, no model#

Owned data + shared-core reads#

Events + cross-links#

Out of scope (simulated + labelled)#

Aggregation + workflow, no model

Owned data + shared-core reads

Events + cross-links

Out of scope (simulated + labelled)