Charles Jones#Incident
6pages on this subject — across the log, the case studies and the documentation.
Entry 006 — Every build minted a review date, and the gate required it
One timestamp file fed both dateModified and lastReviewed across ~61,000 pages, and a pre-build gate refused any build that did not bump it. The estate could not ship without minting the claim.
Entry 005 — One hardcoded state literal, across 14,877 measured pages
Twelve gates came back green while a component told non-Florida consumers their own city was in Florida. A grammatically perfect sentence naming the wrong state is structurally identical to the right one.
Entry 002 — A control was fabricated, then read as evidence
Four artifacts sat in the evidence base as controls. Their bytes never came from the run they claimed to describe, and nothing about the set announced itself as wrong.
Entry 004 — Analytics flatlined, and the flatline read as quiet
Three months of flat line read as low traffic rather than as a dead instrument. The obvious cure was withdrawn because it bought data back by spending the performance standard.
Entry 003 — The www host presented a certificate for a different domain
The www host resolved, redirected to itself over HTTPS, and served a certificate for firebaseapp.com. Visitors met a full-page security interstitial, not a 404.
Entry 001 — A compromised key, and a bill 1,000× the estimate
$11,089.77 billed against $0.71 expected. A compromised service-account key, two banks, and a cure that had to be the absence of the key rather than its revocation.