Reading the brief
DraftThe six figures it leads with, what the model wrote, and what it is not allowed to write.
The six figures, in order
The email and the console lead with the same six figures, in the same order, so the two surfaces rhyme:
- 1Net revenuenet_revenue_daily
- 2Gross revenuegross_revenue_daily
- 3Ordersorders_daily
- 4Average order valueaov_daily
- 5Refund raterefund_rate_daily
- 6MRRmrr_eod
Each one carries the day's value and its distance from the 28-day pace. Every figure is a link: open it and you get the formula, the inputs and the sync that fetched the rows.
What the model wrote, and what it did not
The model never computes a number. Every figure comes from versioned arithmetic over your own orders, and the model writes the sentences around those figures. Before a brief sends, every digit the model wrote is checked against the computed figures. If a check fails, the brief is written once more; if it fails again, you receive the numbers-only brief, with the same figures and the same flags and no prose. A wrong number cannot reach you because a model was confident.
The model can only mention a flag that actually fired. It cannot invent one.
The freshness line
Every brief carries the sync it was built from: which source was read, and when. If a source was stale or a check failed, the brief says so rather than reporting around it.
What velur does not do
velur reports what happened and how it compares. It does not forecast, it does not attribute a change to a cause it cannot see in your data, and it does not replace your accountant.