Integration gaps are a named limitation of the domain and a recurring production failure. A processor adds a column without notice, fields misalign, and the resulting amounts are plausible and wrong — which is far worse than a load failure. Onboarding a new format is currently manual configuration work.
The proposed field mapping, before any data loads. A wrong mapping corrupts every downstream match rather than failing visibly.
Apply a mapping automatically, or continue processing when a schema fingerprint changes. It must halt, not adapt.
Sample file; existing mappings for similar sources; internal schema; historical fingerprints
Proposed field mapping with per-field confidence, plus a change report when an existing format shifts
The domain supports the pattern and no vendor in this model sells it. That is a statement about the market rather than about the pattern; v_agent_gaps lists them.