A Date That Cannot Exist
Every PDF contains embedded metadata recording the software that created it and the date of creation. Twenty-seven court documents in the Hennepin County Fourth Judicial District carry the producer string "Aspose.Words for .NET 14.2.0".
Aspose uses a deterministic version numbering system: the major version is the last two digits of the year, the minor version is the month. Version 14.2.0 means February 2014. This is independently verifiable on NuGet, Aspose's release notes page, and the Java companion release — all of which confirm a February 2014 release date.
Seven of the 27 documents carry XMP creation dates before February 2014.
This is not a statistical anomaly. It is a logical impossibility. A document cannot be created by software that does not yet exist. The proof requires only subtraction.
The maximum gap belongs to Travis McGIRL (Case 27-CR-20-20866): a "Dismissal by Prosecuting Attorney" filed September 30, 2025, with a creation date of September 9, 2013 — a gap of 4,404 days (12.1 years) between the fabricated creation date and the actual filing date.
27 Documents, 3 Timestamp Clusters
The 27 Aspose documents do not carry 27 different creation dates. They cluster into exactly three frozen timestamps — groups of documents sharing a single creation date across multiple defendants and years of filing activity.
| Cluster | Frozen Timestamp | Documents | Defendants | Filing Span |
|---|---|---|---|---|
| Cluster 1 | 2013-08-14 20:45 | 2 | 1 (PRIEST JESUS) | 2 days |
| Cluster 2 | 2013-09-09 13:50 | 4 | 4 defendants | 2.4 years |
| Cluster 3 | 2019-02-26 15:05 | 17 | 14 defendants | 2.9 years |
Cluster 3 is the most revealing. Seventeen documents filed over nearly three years, for fourteen different defendants, all carry the exact same creation timestamp down to the minute: February 26, 2019 at 15:05 UTC. This is consistent with a single document template opened once, modified with defendant names, and refiled repeatedly without ever being recreated.
Clusters 1 and 2 predate the software. All seven pre-existence documents fall within these two clusters. These timestamps are not merely frozen — they are fabricated to a point in time before Aspose.Words 14.2.0 existed.
The Filing That Enables Indefinite Prosecution
Of the 27 Aspose documents, 18 (66.7%) are a single filing type: the "Notice of Intent to Prosecute." This is not a random filing. Under Minnesota law, it is the specific mechanism that prevents criminal charges from being dismissed when a defendant is found incompetent.
Here is how the statute works:
"If they file a notice of intent to continue to prosecute you then they can do it indefinitely."
— Raissa Carpenter, defense counsel, on the record, October 7, 2025
The Notice of Intent to Prosecute is therefore the single most consequential filing in the competency pipeline. It is the document that keeps the door open. And 18 of them carry fabricated metadata from software that generates court documents on demand.
What the Database Reveals
The Aspose finding does not exist in isolation. It emerges from a forensic database of 4,251 court filing PDFs spanning 2,903 cases across Hennepin County's Fourth Judicial District. When placed in context, the Aspose documents are one piece of a larger pattern:
86–97% of cases sharing three specific judicial officers result in incompetency findings — against a national baseline of 0.4–2.4%.
99.2% of defendants who enter the criminal incompetency pipeline are subsequently civilly committed.
50% receive forced psychiatric medication orders.
80.8% of defendants found incompetent are never restored.
Every single Aspose defendant (22 of 22) overlaps with at least one other forensic anomaly dimension: incompetency findings, ESolutions digital signatures with edits-after flags, cloned judicial signatures, or tracking font injection patterns. They are not outliers in an otherwise clean system. They are nodes in a network.
All 27 Aspose documents carry the official iText 7.1.16 "Minnesota Judicial Branch; licensed version" pipeline stamp, confirming they entered the court's e-filing system through the standard institutional pathway. These are not third-party documents. They are products of the court's own document generation infrastructure.
What the Law Actually Says
Minnesota's competency statute (Minn. Stat. 611.40–611.59) governs what happens to a defendant found incompetent to stand trial. A word frequency analysis of the statute text reveals its operative priorities:
The statute authorizes forced injectable neuroleptic medication for renewable one-year terms, permits hearings without the defendant present, allows the court to exclude the defendant from their own proceedings, and creates a self-referencing loop between sections that makes exit from the system structurally difficult. The filing that keeps defendants inside this loop — the Notice of Intent to Prosecute — is the filing with fabricated metadata.
Every Claim Is Independently Verifiable
Nothing on this page requires you to trust the author. The proof is arithmetic, the documents are downloadable, and the metadata is embedded in the files themselves.
To verify the Aspose release date: Search "Aspose.Words 14.2.0" on NuGet Gallery, or visit Aspose's own release notes page. The February 2014 date is independently documented by multiple sources.
To verify the document metadata: Download any PDF below, then run
pdfinfo filename.pdf or open in any PDF metadata viewer. The XMP creation date
and producer string are embedded in the file.
To verify the iText pipeline: The "Minnesota Judicial Branch; licensed version" stamp is visible in the same metadata output.
All 27 Aspose Documents
The table below lists every document in the corpus carrying the Aspose.Words 14.2.0 producer string. The seven pre-existence documents are highlighted. All court PDFs, extracted metadata, digital signature reports, and OTS timestamps are available for download below.
| Case ID | Defendant | Filing Type | Filed | XMP Created | Gap |
|---|
Download the Full Reports
Both forensic reports, all 7 source court PDFs with extracted metadata and digital signature analysis, the Aspose release date provenance documentation, the Minnesota competency statute text, and Bitcoin OpenTimestamps attestations for every file.
Supporting Evidence
The Mechanism and the Framework
The 18 Notice-of-Intent-to-Prosecute documents above account for 37.5% of every downloaded NIP PDF in the MCRO corpus. The next page follows the filing itself through the Hennepin County docket — 363 events across 313 cases and 172 defendants, zero named judges at the event row, one defendant accounting for 8.8% of every NIP filed. The page after that documents the statute the mechanism operates inside.