Reference solution for taking one business analysis question through interpretation, data-source and query planning, query generation and execution, deterministic result preparation, analytical reasoning, optional validation, and a business-facing analysis output.
Unit event
Analysis Request
ANALYSIS_REQUESTOne business analysis question taken through interpretation, data-source/query planning, query generation and execution, deterministic result preparation, analytical reasoning, optional validation, and production of a business-facing analysis output.
Design variant
Up to three data sources, five fixed query occurrences, a larger prepared result, two analysis passes, an explicit validation pass, four charts, a detailed report.
Every value this design resolves, and who owns it. Change an editable value and the figures recalculate. The pricing engine answers, not this page: nothing here multiplies anything, and until it answers the figures beside you are the ones you were already looking at, labelled as such.
65 fields
Estimated tokens in the business question.
Estimated tokens of supplied business context.
Input tokens eligible for cached-input treatment.
Estimated generated objective tokens.
Estimated system/policy prompt tokens.
How much of the analysis objectives this step reads.
Input tokens eligible for cached-input treatment.
How much of the data catalog this step reads.
Estimated generated query-plan tokens.
How much of the normalized question this step reads.
Estimated planning instruction tokens.
Input tokens eligible for cached-input treatment.
Estimated generated query tokens.
How much of the normalized question this step reads.
Estimated tokens of prior-query context read by an occurrence. Flat per occurrence: §7 forbids per-occurrence dataflow.
Estimated query-generation instruction tokens.
How much of the query plan this step reads.
How much of the schema this step reads.
Estimated tokens of the returned result — the quantity that does reach a model, kept separate from the rows scanned on purpose.
How many rows came back. A workload fact.
How many source rows the warehouse scanned. A workload fact and nothing else: it reaches no meter, no binding and no usage expression, and Deep scans a thousand times what Quick does for the same price.
How many metrics were derived. A workload fact.
Estimated tokens of the prepared dataset.
How much of the prepared dataset this step reads.
How much of the findings this step reads.
Input tokens eligible for cached-input treatment.
How much of the derived metrics this step reads.
Estimated generated validation tokens.
Estimated validation instruction tokens.
How much of the prepared dataset, per occurrence this step reads.
Estimated analysis instruction tokens.
Input tokens eligible for cached-input treatment.
How much of the derived metrics this step reads.
Estimated generated findings tokens.
How much of the normalized question this step reads.
How much of the prepared dataset this step reads.
How much of the findings this step reads.
Input tokens eligible for cached-input treatment.
How many chart specifications are produced. Explanatory: rendering is not billed.
Estimated generated report tokens.
How much of the normalized question this step reads.
Estimated report instruction tokens.
How much of the validation notes the report reads; zero when no validation ran.
Where the direct unit cost comes from. Expand an operation for the activities inside it and how each one resolved.
Interpret the business question and state the analysis objectives.
Interpret Analysis Request
PricedNormalize the business question and state what the analysis is for.
A pricing request was made and returned an amount.
Identify the data sources and produce a query plan.
Plan Data Analysis
PricedIdentify the data sources and produce a query plan. Priced on its own; §9 forbids folding it into the analysis budget.
A pricing request was made and returned an amount.
Generate the queries and run them against the warehouse. The execution is external and unpriced: rows scanned are not tokens.
Generate Data Query
Priced×5Write the query text from the plan and the schema.
A pricing request was made and returned an amount.
Execute Data Query
No pricing request×5Run the query against the warehouse. External and unpriced: the catalogue has no canonical scan meter, and inventing one would price a row as though it were a token.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Prepare the result deterministically and check the findings against it.
Normalize Analysis Results
No pricing requestSort, filter, group and derive metrics locally. This is the real analytical arithmetic and it is unpriced: a deterministic calculation does not become a model charge because a model later reads it.
This activity does not price. No request was made, so there is no amount — not an amount of zero.
Validate Analysis Findings
PricedCheck the findings against the dataset and its metrics.
A pricing request was made and returned an amount.
Reason analytically over the prepared dataset.
Analyze Business Results
Priced×2Reason analytically over the prepared dataset.
A pricing request was made and returned an amount.
Write the business-facing report and its chart specifications.
Produce BI Analysis Output
PricedWrite the business-facing report and its chart specifications. TEXT out: a chart specification a UI may later parse is not a STRUCTURED_DATA model contract, and rendering a chart is not a charge.
A pricing request was made and returned an amount.
Direct unit total
0.231915 USDBars show each operation’s share of the stated direct unit total. An operation with no priced activity shows no amount, which is not an amount of zero.
Activity states not exercised by this configuration
The read model reports these so their absence reads as absence rather than as coverage.
Issues
The runtime reported none for this configuration.
Technical detail and reproducibility