Evidence Validation
The evidence validation engine applies rule-based checks to extracted field values. Results appear as colored validation badges in the Evidence tab of the case detail page.
Structural validators (S1–S7)
| Parameter | Type | Description |
|---|---|---|
| S1 | rule | Free-text spillover — field value contains unstructured text that leaked from adjacent content. |
| S2 | rule | Empty value — required field is blank or whitespace-only. |
| S3 | rule | Email/URL misclassification — value looks like an email or URL but is in a non-email/URL field. |
| S4 | rule | Name in URL field — a person or company name extracted into a URL-typed field. |
| S5 | rule | Alpha in numeric field — alphabetic characters in a field expected to be numeric. |
| S6 | rule | Cross-field duplicate — identical value appears in multiple unrelated fields on the same document. |
| S7 | rule | Checksum validation — Luhn (credit cards), ABA (routing numbers), IBAN, ISBN checksums verified via parameterized factory. |
Domain packs extend validation with industry-specific rules. The freight domain pack includes DOT number state detection and MC number validation. Additional packs can be added to domain-packs/ without modifying the core engine.
Evidence validation results are stored in a separate
evidence_validation_results table keyed by (document_id, entity_id, field_key) — not in the extraction or linking tables.