Field note / Financial analysis
Entity, metric, period and snapshot are part of correctness.
What breaks
Compare the intended question with the routed query and returned financial context. A successful API call only establishes that a response was received; it does not establish the right entity or reporting period.
Challenge the fix
A deliberately requested historical snapshot should not be rejected merely because a newer one exists.
Worked example · fictional records
Question Q-8 · entity A · FY2025
Evidence to inspect
The SQL succeeds, but returns entity B for FY2024.
What would establish the fix
Pin entity, metric, period and source snapshot; compare those fields before grading the answer.
Counterexample
A numerically plausible value still fails when its business context is wrong.
This example explains the check. It does not report a customer result or a completed production run.
Explore the reliability workflow ↗
How the lesson shapes Tensile
Checks pin context separately from retrieval and answer quality. Keep role access in the same execution manifest.
Explore this product area ↗
Anonymized engineering lesson. Example records are reconstructed for this preview; this is not a published customer case study or a measured result.
All field notes ↗
AI reliability, from production to customer outcome.