Provenance Starts Before The Review Screen Document provenance is easy to postpone. The first version of a workflow only needs to read a PDF, pull out a few fields, and send them somewhere useful. The team can add review screens, audit dashboards, and source inspection later. Then the workflow works. Customers depend on it. A field is wrong. A generated report contains an unexpected value. Someone asks which document produced it, which extraction schema was used, whether a human changed it, and whether the corrected value was sent downstream. If the answer is hidden in logs, webhook payloads, and old model responses, provenance has become a cleanup project. The mistake is treating provenance as a feature that only exists when there is a polished reviewer interface. Interfaces are useful. They are not the foundation.…