Correction
corr-2026-07-20-missing-published-days
Logged: 2026-07-20
Severity: major
Status: resolved
Affected record: 2 days (2026-07-12, 2026-07-18)
Affected day pages: 2026-07-12 2026-07-18
Timeline: detected 2026-07-20; acknowledged 2026-07-20; corrected 2026-07-20.
Original rendering unavailable · Corrected rendering unavailable
What happened
The composite Daily Lines and talking points for two already-published days went MISSING from this site. The daily collection run rewrites the day record it is working on, and when it landed on a day that had already been published it overwrote that day's composite half with nothing — deleting the two party composites, their talking points, and the day's cross-party phrase pairings. Nothing published was WRONG: no number changed, no citation broke, and the underlying record of what members actually said was never touched. Content that had been published simply stopped being there, and one day's page went on displaying composites whose backing data had been removed. Because every surviving number stayed correct, no receipts audit or citation check could have surfaced this — it is an absence, and the verifier has no opinion about absence. It was found by the pre-launch health review, before this site had an audience.
Resolution
Both days were restored from the exact content originally published, read back out of this project's version history — not regenerated. That distinction is the point: re-running the composer today would have written new prose, under a newer model and a newer prompt, and presented it as what we said on those dates. The restored text is byte-for-byte what was published, including one day whose composite was always a deterministic template rather than a language model, which is labelled as such. A third day (2026-07-09) was deliberately NOT 'restored': it never carried composites, because the composer never ran for it, and manufacturing one now would invent a record rather than repair it — it remains listed as a phrases-only day. The cause is closed in code: a day that has been published is now immutable to the collection run, which skips it and says so, and the only path that may write to a published day is the explicit repair path. Both parties, one rule, no threshold changed.