The Upload Says PDF. The Business Says Packet. Sooner or later, a document workflow receives a file that is not really a document. It might be a 180-page PDF from a supplier. The first pages are a cover letter. Then comes a signed contract, a tax certificate, bank details, insurance documents, delivery notes, an invoice table, two scanned IDs, and a few pages that are sideways because somebody merged the packet in a hurry. Your storage layer sees one upload. Your queue sees one job. Your extraction code sees one blob of bytes. The business process sees a packet. That distinction matters more than page count. Large packets do not only break extraction pipelines because they are long. They break because they combine several kinds of evidence for several decisions. If you process the whole thing as one document, fields collide, context gets noisy, failures become all-or-nothing, and review turns into a scavenger hunt.…