Can a release include defective, stale or conflicting documents?
Answers what defect types a release can carry, whether documents are full files or structured text, whether labels are hidden from the agent, and how combined defects can be requested.
**Can a release include defective or conflicting documents?** Yes. A buyer can ask for defect types to be generated and tagged so they can be controlled and scored.
**Which defects are typical?** - Missing item - Expired or not yet valid - Issued to the wrong party - Unsigned or incomplete - Illegible or truncated - Duplicate of an item already supplied - Two documents that disagree on a value
**Are documents full files?** Scope this in a pilot. A release can carry structured fields plus generated text for each document, and a pilot can test whether page images or scanned layouts are needed. Many environments only need the fields and text the agent will read.
**Are the defect labels visible to the agent?** They can be held back. The agent sees the document content; the label sits in the grader's answer key. A buyer can also ask for a version with labels exposed for supervised or debugging use.
**Can defects be combined?** Yes, and combined defects are worth requesting, since an agent may fix the first gap it finds and stop. Ask for cases with two or three gaps, and for cases where a defect looks serious but a held record resolves it.
**Is this real customer paperwork?** No. It is generated. Inspect samples for grounding, and for any resemblance to real documents that would create disclosure risk, before use.
Defects can be generated, tagged and combined under buyer control, with labels held in the answer key so the agent only sees document content.
- Audience:
- Environment builders
- Content type:
- FAQ
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- Which records and relationships can a sufficiency dataset or task pack contain?
- Will a release include the documents themselves, or only metadata about them?
- What might the JSONL or Parquet schema look like for sufficiency cases?
- What should I include in a release specification for a sufficiency task pack?
- What would a generated insurance case with conflicting documents contain?
- How can one freight import case be expanded into controlled variants?