Validation-retry loops for extraction quality

What the exam expects

• Tell a schema syntax error (which strict tool use eliminates) from a semantic error (values that do not sum, a value in the wrong field) and put business-rule validation in application code.
• Build a retry-with-error-feedback step: a follow-up that carries the original document, the failed extraction and the specific validation errors, or a tool_result with is_error: true that names the fields and rules.
• Predict when a retry will work (format mismatches, structural errors) and when it cannot (the information is absent or sits in a document that was never sent), and route the second case instead of retrying.
• Design self-correction fields such as calculated_total beside stated_total and a conflict_detected boolean.
• Add a detected_pattern field to structured findings so dismissals can be analysed by pattern.

Key terms: syntax error (output that does not parse or match the schema); semantic error (schema-valid output whose values are wrong); retry with error feedback (re-asking with the specific errors attached); self-correction field (a schema field that lets a discrepancy be recorded instead of hidden); dismissal analysis (grouping rejected findings to find false-positive patterns).

Key facts

Check yourself