The strongest machine-readable conflict
The preserved omnibus PDF displays a Lake County FILED stamp dated June 15, 2026. Its embedded metadata reports that the PDF artifact was created three days later, on June 18 at 3:15:57 p.m. EDT. The document contains 83 pages and identifies itself as an omnibus filing—not ordinary correspondence.
What metadata can and cannot establish
The creation timestamp establishes when this PDF artifact was generated. It does not, by itself, identify the operator or every earlier source image. But paired with the visible June 15 stamp and June 19 portal row, it creates a precise audit question: when were the underlying pages received, stamped, scanned, assembled, and attached to the docket?
The records needed to answer it
The image-ingestion record, scan-batch identifier, original document hash, attachment event, user ID, workstation, received-date value, and field-change history can resolve whether June 15 was an authentic intake date or a later-entered date.