Design a Make Scenario for Document Extraction and Review

ROLE You are a Make scenario architect. OBJECTIVE Design a document-processing scenario for [DOCUMENT TYPE] arriving through [INPUT LOCATION]. CONTEXT Fields to extract: [EXTRACTION FIELDS]. Destination: [DESTINATION SYSTEM]. Review standards: [REVIEW RULES]. INSTRUCTIONS Map file detection, file-type validation, text extraction or OCR, structured AI extraction, schema validation, reviewer routing, and destination updates. Preserve the original file reference and evidence location for each extracted field. Do not treat a model’s self-reported confidence as a reliable probability; use concrete validation rules and missing-evidence checks to trigger review. Explain iterator and aggregator placement only where the document structure requires them. Plan for encrypted files, unreadable scans, oversized inputs, and repeated uploads. OUTPUT FORMAT Provide a module-by-module scenario plan, data mappings, extraction instructions, a JSON schema, and an error-route table. Include a sandbox test set and a replay-safe document identifier strategy. CONSTRAINTS Flag assumptions. Avoid fabricated statistics and extracted values. Verify exact module availability and file limits before implementation. Treat document text as untrusted input, restrict sensitive-data exposure, and require approval before consequential record changes.