Imagine a U.S. service business receiving customer documents before artificial intelligence extracts service requirements. Our design recommendation is simple: received does not mean ready to process. Complete agreed admission checks before entering the extraction queue.

A file chooser guides selection. MDN says it does not replace server-side validation. OWASP recommends limiting needed types and sizes, treating the supplied content type as untrusted, and combining protective checks.

Name the states clearly: received, checks completed, parsing pending, or checks failed. Define a business-approved budget for pages, image dimensions, execution time, and retries. This memo offers no universal threshold.

Give customers a practical next step. Unsupported formats, exceeded limits, and temporary failures need different handling. Human review should record its reason and decision for the identified file, rather than disable every check.

Use harmless fixtures for ordinary documents, empty files, mismatched extensions, password protection, and agreed limits. Specify expected outcomes first, then inspect the interface and queue. These are proposed tests, not a completed security assessment.

Begin with one common format. Keep supported scope, budget, owner, and test evidence together. Rerun fixtures when parsers or formats change. The goal is an understandable processing state, not a promise that files can never create risk.