Field note / Document review
A clean queue can hide an obligation that never became a finding.
What breaks
Start with an independent obligation inventory across the eligible file. Bind each obligation to the applicable source region, party and policy revision. Only then compare it with the generated findings.
Challenge the fix
A correctly completed file should produce no finding; the coverage check must still account for its obligations.
Worked example · fictional records
Obligation O-17 · source page 8
Evidence to inspect
An independent whole-file inventory includes O-17. The extraction inventory and finding queue both omit it.
What would establish the fix
After the extraction fix, account for O-17 and its source region before judging the finding.
Counterexample
A compliant file has zero findings but still needs complete obligation coverage.
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
Keep extraction, interpretation and checklist failures distinct. Investigate begins with the missing obligation; Evaluations retains whole-file coverage.
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.