Parcel retries keep failing because the needed grantor name exists only in an external deed not in the packet. What should the architect conclude?
Select an answer to reveal the explanation.
Short Explanation
You can't find a key in a drawer that was never opened—if the grantor lives only in another deed, retries won't conjure it. Stop looping and fetch the missing source.
Full Explanation
If parcel retries keep failing because the grantor name exists only in an external deed that was never placed in the extraction packet, the architect should conclude that retries are ineffective when required information is absent from provided inputs. Validation-retry loops can fix formatting, field placement, and schema shape; they cannot recover facts that are not present in the materials supplied to the model. Continuing to loop burns compute, delays clerks, and raises fabrication risk as the model fills gaps with plausible names. Raising temperature until the model invents a plausible grantor actively encourages hallucination and is unacceptable for municipal property records where wrong parties create legal exposure. Assuming schema validation alone invents missing deed fields confuses syntactic enforcement with knowledge retrieval—schemas check structure, not whether the deed was scanned. Unlimited retries never recover fields that were never supplied; they only amplify cost and error. Exam caveat: distinguish retryable extraction defects from missing-source defects that require fetching another document or escalating to a human. Operational check: when the same required field fails after a bounded retry budget, verify the source inventory for that parcel, fetch the missing deed if it exists, and only then re-run extraction—do not keep prompting the incomplete packet.