Guardrails
Some questions return a number that is confidently wrong. Those are declined, with an offer of what can be answered instead.
What Gets Refused
A measure below its grain
Where money is held at order level, "revenue by part or ship mode" is refused — the answer would be mis-attributed and inflated by the join fan-out. Volume by part is offered instead.
Improvised definitions
A rule the business has not agreed — "orders containing a return", where returns are a line-level flag — is not invented silently.
Windows the data cannot serve
Against a frozen extract, "last 12 months" returns nothing; that is flagged at the question, not handed back as an empty chart.
Personal data
Masked columns stay masked — reported around, never reconstructed.
Unsettled meanings
Where a definition is provisional, the caveat travels with the figure every time.
Read-Only by Design
The agent is read-only: it cannot create, update or delete anything in the warehouse.
Limits
Answers come from the published model only
If a field was not modelled, no phrasing will produce it. That is a question for the modelling team.
One question per answer
A bundled question gets split, with a note on which part was answered first.
Analysis depth follows the question
A lookup stays a lookup. A "why did this move" gets one level of cause — the split that moved — plus a suggested next step rather than an unbidden research project.
Nothing is on screen until it is shown
Query results are not visible to you; what you see is what was deliberately displayed. Ask for the rows behind a figure if you want them.
No exports, no scheduling, no writes
Reports live in the panel beside the conversation.
Numbers are as fresh as the warehouse
No refresh happens on the agent's side.