Every source is tied to the tenant composition it feeds, its evidence basis and its honest fallback.
Data sources
Where every number on these workspaces comes from, when it was last refreshed, whether it is measured or an estimate, and what stands in its place when it is absent.
2 of the 2 measured money feeds are not connected, so the dollars they would have measured are shown as a labelled estimate everywhere they appear — the figure is never missing, the word on it changes. counted
Every source, and what stands in its place when it is absent
The last column is the one to read if you are deciding whether to trust this product: it says what happens to each number when its source is not there.
1 filter active Showing 2 of 29 sources, role projection.Change
1 filter active Showing 2 of 29 sources, role projection.
Scroll sideways for the remaining columns.
| Source | What it feeds | Role & basis | Its own freshness | Consent, and what stands there without it |
|---|---|---|---|---|
| The spend projection
Aristo
src/enterprise/forecast.ts · projectSpend |
Where this month's spend is heading, on the analytics workspace.
Fields: spendProjection |
projection
Answering |
— no stamp of its own |
Inherits the money feeds it extrapolates from
If absent: The projection is withheld and the page says how much history is still needed.
Turns on: It needs enough history. Below that it returns "needs more history" rather than a line through two points. |
| The score trajectory
Aristo
src/enterprise/frontier.ts · projectScoreTrajectory |
The "on pace to cross into the next band" sentence, where there is enough history to support one.
Fields: trajectory |
projection
Answering |
— no stamp of its own |
Inherits the score
If absent: The sentence is simply not written. It is withdrawn the moment the trend stops supporting it rather than being restated with a smaller number.
Turns on: Three runs and a band crossing within ninety days. Anything less returns nothing. |
How to read source roles
A read is something Aristo asked a system for. A computed figure is produced by an engine over those reads. A projection describes an unfinished period and is always labelled as such.
The field map
The mechanical contract behind this page: every value these workspaces read, and the source it is claimed from.
Every workspace reads the same composed view. This mechanically tested crosswalk names the source behind each field.
Show all 43 fields and their sources
Scroll sideways for the remaining columns.
| Field | Fed by |
|---|---|
activationPct | Microsoft Graph — Copilot usage reports |
agentInventory | Microsoft Graph — agent registry (beta) |
agentsBuilt | The forged-agent register |
bli | Business licence inventory |
budgetEnforce | This organisation's own settings |
cmUsage | Azure Cost Management — reconciled export |
coworkBudgetUsd | This organisation's own settings |
creditBasis | Azure Cost Management — reconciled export |
creditPct | Azure Cost Management — reconciled export |
demo | Aristo's own run history |
deptRows | Microsoft Graph — directory departments |
deptTrend | Month-grained product and department history |
deptUtil | Microsoft Graph — seat map and department utilisation |
depts | Microsoft Graph — directory departments |
frontier | The Frontier score engine |
generatedAt | The composition instant |
history | Aristo's own run history |
idleSpendMo | Microsoft Graph — Copilot usage reports |
license | Microsoft Graph — licence truth |
licenseEconomics | Microsoft Graph — licence truth; The licence economics engine |
moves | The strategy engine |
narrative | The strategy engine |
org | The tenant registry |
plans | Move plans and their completion |
prev | Aristo's own run history |
productTrend | Month-grained product and department history |
radar | Microsoft 365 Message Center and the public roadmap feed |
readiness | The readiness engine |
runNumber | Aristo's own run history |
seatCost | This organisation's own settings |
seatRows | Microsoft Graph — seat map and department utilisation |
seatRowsWithheld | Microsoft Graph — seat map and department utilisation |
seatSlices | Microsoft Graph — seat map and department utilisation |
shadowAi | Microsoft Graph — sign-in audit logs |
skillDownloads | The skill shelf |
skillsOnShelf | The skill shelf |
sliceLabels | Microsoft Graph — seat map and department utilisation |
spendLights | Copilot credits report; The spend-light engine |
spendLightsWithheldK | The spend-light engine |
spendProjection | The spend projection |
spendTrend | Azure Cost Management — reconciled export; Copilot credits report; The spend-light engine |
stats | Microsoft Graph — Copilot usage reports |
trajectory | The Frontier score engine; The score trajectory |
What this page does not claim
The design system asks that every result carry seven things. Aristo carries five of them, and here is the honest account of the other two.
Every figure carries its source, period, freshness, basis and shared definition. Open the exceptions only when you need the methodology detail.
Read methodology limits and exceptions
Carried on every figure: the source it came from; the period it covers, where the source is periodic; when it was last refreshed, using the stamp the data itself carries; whether it is measured, counted, attested, provided, an estimate, an assumption or a projection; and the definition, through the shared metric vocabulary that means a word never changes meaning between two screens.
Not carried: a confidence interval on most figures. Aristo publishes one only where it has actually computed one — the never-nudged holdout comparison bills on the lower bound of a ninety-five per cent interval, and says so. Attaching a confidence figure to a counted seat total would be decoration: the count is either right or the read failed, and there is no distribution to describe. Where a figure is genuinely uncertain the product's answer is the basis word and the withheld state, not a percentage nobody computed.
Not carried: a single methodology paragraph per figure. The methodology is on the workspace where the figure appears — beneath the chart it was drawn from, in the evidence line under the number, and in the "view the data behind this chart" panel that shows the rows. Restating it here would create a second description of the same method, and two descriptions of one method eventually disagree. This page names the source; the workspace explains the arithmetic.
And one caveat that belongs at the top rather than the bottom. The "as of" stamp in the shell is the moment Aristo composed the view, and the composition is cached for forty-five seconds. It is not a statement about when Microsoft collected anything. Where a source carries its own stamp — an export's ingest time, a crawl's fetch time, a feed's update time — that stamp is in the table above and it is the one to believe.