User Journey

An executive asks for a number. The planner routes the text to one of four governed views by keyword, picks a measure and a dimension, and builds a parameterized, aggregates-only query. A guard step enforces the PII-free view; the query executes against the governed aggregates; a narrative summarises the top group as a share of the total. The whole turn is metered: a cost row and a trace are written for the inspector.

The governed views BI Chat reads are roll-ups of the same shared entities the ecosystem runs on — bookings, reviews, guest segments, partner scorecards — so an answer here is consistent with what #24 KPI alerting watches and what #27 FinOps prices. Each ask emits a cost.logged event that #27 aggregates, and the metered stage's prompt is the one #29 ModelOps governs. BI Chat is a reader at the safe end of that spine.