-
Notifications
You must be signed in to change notification settings - Fork 1
Validation System
Sinbad Adjuik edited this page Apr 6, 2026
·
1 revision
The application validates runs before and after packaging.
This helps catch:
- missing outputs
- invalid ZIP structure
- patent manifest issues
- patent PDF lookup failures
- dry-run violations
Before processing begins, the tool checks:
- output write access
- available disk space
- scratch workspace readiness
- configured patent fallback roots when patent mode is active
After non-failing runs, the tool validates:
- expected ZIP count
- actual ZIP count
- workflow-specific ZIP structure
Workflow-specific ZIP expectations:
- photo workflow:
TIFF + XML + manifest.ini - patent workflow:
PDF + XML + manifest.ini
The reconciliation report compares:
- input XML count
- CSV success row count
- actual ZIP count
- valid ZIP count
This makes it easier to spot silent skips or mismatches after large runs.
Dry run validation expects:
- zero ZIP files created
If ZIP files appear during dry run, the validation report flags that as a problem.
Patent runs require a shared manifest with:
- a
[package]section - required package fields present and non-empty
The validator does not enforce one fixed set of values.
Last updated: April 6, 2026