Mixed document packs need triage before they need smarter extraction

Most document pipelines are easier to build when you assume each upload is one self-contained document with one obvious role. That assumption breaks quickly in production. Real workflows often receive mixed packs: an invoice plus a receipt, a KYC form plus an ID, a claim form plus supporting pages, or a trade packet with primary and secondary documents mixed together. If all of that goes into one extraction path unchanged, downstream interpretation becomes much harder than it needs to be. What broke In practice, the failures did not look dramatic. They looked operational. Supporting pages were interpreted like primary pages. Partial packets were handled like complete submissions. Similar-looking fields competed across pages that served different roles. Reviewers spent time figuring out page purpose before they could judge extraction quality. Schema logic got more complicated because the intake stage had already thrown away too much context. This is why a lot of “extraction issues” are