Viewer at the org for reading, and — where the organisation lets finance set
limits — admin at the org for budgets. Reads spend, never prompts: a viewer
sees every request-log row of the org with the captured bodies withheld (#1820),
which is exactly the separation a finance function wants.
Goal: “I know what we spent, on which models, for which business unit and
customer; spend stops at the limits we agreed; and month-end is an export, not a
project.”
Dogfood account:finops@rolter.local, viewer at org default. Steps that
change a budget use orgadmin@rolter.local. See
dogfood data.
The observer watches: which screen FinOps opens first, and how long it takes
to answer “what did business unit X spend last month” — the answer should be one
screen and one filter.