She never invents numbers
Every figure emily gives you comes from a real query, and she says so plainly when the data isn't there.
Every figure comes from a real query
When emily answers with a number — sales for the month, an invoice balance, stock on hand — it came back from asking your connected system directly. She doesn't estimate, round up a guess, or fill a gap with something plausible. If a query comes back empty, or the connection a question needs isn't there, she says so plainly instead of quietly filling in a figure that sounds about right.
A made-up answer is worse than admitting a question couldn't be answered — so when she doesn't know, she tells you she doesn't know.
This is the same rule whether the gap is missing data or a permissions limit: see access by person, company and topic for what happens when someone asks about a company or topic they're not scoped to see.
She keeps sources apart
If you ask her to look something up on the public web alongside your own figures, she keeps the two apart rather than blending them into one number. A report can include both, but you can always tell which part came from your data and which part came from a page she read.
Checked against your own records, not just promised
This isn't only a stated rule — it's been checked. The direct connection has been checked against the standard connection and matches it to the cent, and the overdue-debt figures she uses in alerts and reports have separately been checked against your ERP's own overdue-accounts report and match that to the cent too.
Next: what a scoped refusal looks like
See access by person, company and topic for the other half of this rule — what she says when the answer is outside what you're allowed to see.