
Ten validation cases, each with a downloadable synthetic document set (fictional parties, realistic layouts) and a caption of exactly what Nova catches. Pick one, open the document flow and watch the same class of error get caught.
Nothing wrong — the zero-touch path.
Nova catches: All 22 rules pass — filed and acknowledged with zero human touch.
Seeded: Commercial invoice missing the incoterm; an unexpected surcharge line added.
Nova catches: Flags the absent incoterm and the unrecognized line item; asks the sender for one, files the rest.
Seeded: Container gross weight on the BL disagrees with the invoice packing summary by 1,240 kg.
Nova catches: Cross-checks every shared field against the booking — weight, qty, consignee, incoterm — and pins the exact delta.
Seeded: A skewed, low-DPI scan on a non-standard carrier template.
Nova catches: Extraction confidence drops below threshold → routed to human review instead of guessing.
Seeded: The same document set re-sent two days later with a new email subject.
Nova catches: Content-hash match against the earlier filing — acknowledged as duplicate, nothing double-processed.
Seeded: Certificate of Origin arrives after the vessel's document cut-off.
Nova catches: Deadline breach detected on arrival; escalation with the cost of delay already computed.
Seeded: BL and packing list agree; the invoice names a different consignee entity.
Nova catches: Validates the set as a unit — two documents pass, the third is quarantined with the mismatch named.
Seeded: Invoice totals in USD against a EUR-contracted rate; one HS code from the wrong chapter.
Nova catches: Contract-aware checks: currency vs the rate agreement, HS code vs the product master.
Seeded: Original BL without the carrier's issuing stamp block.
Nova catches: Layout-level check — the stamp region is empty; flagged before customs would bounce it.
Seeded: First submission has a wrong invoice total; the corrected version arrives on the same thread.
Nova catches: Reply → resubmit → re-validate on one thread; the audit trail shows both versions and who changed what.
All documents are synthetic — fictional parties and cargo, generated from the case taxonomy (kb/reference/drdv-cases.md). Never attribute them to real accounts.