# Sources and scope — Stopping a Shared Fault Is Not the Same as Repairing Its Consequences

1. John Graham-Cumming, [“Details of the Cloudflare outage on July 2, 2019,” Cloudflare, July 12, 2019](https://blog.cloudflare.com/details-of-the-cloudflare-outage-on-july-2-2019/). See “Events of July 2,” “What happened,” deployment and “What went wrong” sections. This is a first-party retrospective, not an independent audit or an AI study. The report distinguishes detection, global WAF termination at 14:07 UTC, expected traffic/CPU levels by 14:09, and WAF restoration at 14:52. It supplies no complete request-level harm or remedy accounting.

2. [“Statement from Roger Taylor, Chair, Ofqual,” August 17, 2020](https://www.gov.uk/government/news/statement-from-roger-taylor-chair-ofqual). The statement acknowledges appeals burden and distress and announces centre-assessment or moderated grades, whichever is higher. It is a policy announcement, not verified implementation timing, an accuracy evaluation or proof of repaired downstream consequences.

The historical discussion uses retained primary captures checked on October 22, 2026; both public pages were independently reopened for this commentary on November 5. No underlying incident logs, individual student records, full Ofqual technical evaluation or new participant data were analyzed. The follow-up comparison is explicitly synthetic and supplies no empirical parameters or numerical AI gains.

This commentary extends the Institute's [Judgment Saturation essay](https://recursive.institute/articles/judgment-saturation-and-the-burnout-to-bypass-pipeline/) and [Machine Spirits](https://recursive.institute/articles/machine-spirits-algorithmic-markets/). Their existing architectural-intervention arguments are acknowledged, not claimed as a new discovery. No historical essay or pending correction is revised by this commentary.
