A parcel extract fails schema checks. How should the retry be framed for correction?

When a municipal parcel extract fails schema validation, the retry must give the model everything needed to correct a targeted mistake: the source document, the failed JSON, and the specific validation errors. That combination mirrors returning a permit form with circled fields—the model can see what was intended, what it emitted, and why the checker rejected it. Omitting any of those three leaves correction underspecified. Retrying with a blank prompt that hides prior failures forces the model to rediscover the same bugs without feedback and wastes tokens on repeated identical mistakes. Deleting the schema so any shape can pass converts a quality gate into an open sink and undermines structured intake for assessor or recorder systems. Retrying only the failed JSON without returning the source document asks the model to invent fixes from memory of a prior parse rather than re-grounding in the deed or parcel packet. Exam caveat: retries improve recoverable format and placement errors; they do not create facts absent from inputs. Operational check: log each parcel retry payload and confirm the next attempt includes document bytes or text, prior JSON, and validator messages keyed by field, then measure whether error codes actually decrease on the second pass.