Results and provenance

A metric result stores its period, dimension key, numerator, denominator, value, source row count, status and reason. It can link to a retail snapshot, metric definition and operation run. This lets the Retail Analyst answer a practical question: which source scope and approved definition explain the figure shown for a store period? A result marked suppressed or invalid should remain visible as an exception with its reason.

An operation run carries the operation key, frozen source revision, start and completion times, input hash, result reference and failure reason. Its numbered steps retain action names, input and output references, receipt state and any external receipt evidence. That detail is useful when a collection is interrupted. It distinguishes a completed result from a request whose outcome still needs reconciliation.

• Result. The value and component counts stay with their period, dimension and status.
• Run. The operation key and source revision identify the exact execution context.
• Steps. Numbered actions and receipts explain what was attempted and what was confirmed.

Agree how the team chooses an eligible basket-fact scope for a result and which metric definition governs it. Confirm how a zero denominator is represented. A conversion rate should not appear as an ordinary calculated value when the denominator is zero. Agree how to reconcile a failed collection run, and keep any related result identity visible while that decision is made.

The reviewer should have a way to inspect the source row count and component values. A headline rate may move because the numerator changed, because the denominator changed or because the source window changed. Those are different issues and need different follow-up actions.

Open one reviewed store snapshot and the metric result for its period. Compare the linked metric definition with the recorded numerator, denominator and value. Check the source row count. If the result links to a run, inspect its frozen revision and numbered steps before relying on the recorded outcome. If the operation is marked for reconciliation, the Operations Lead investigates that record before the result is used.

Now compare a later period with a changed source window. The analyst should be able to explain the change from the stored period and source context, rather than editing the original result to make the trend look consistent. Keep exceptions visible in the Retail Overview follow-up queue.

• Result windows — Compare result values by metric, period and dimension.
• Result exceptions — Inspect suppressed or invalid outcomes and their reasons.
• Operation reconciliation — Find runs that failed or need a result check.

Follow definition to result and handle an exception.