Provenance Record

Clean, well-structured News piece (422 words, within the 400-1200 News range). Clear Overview/What Happened/The Fix/Context sections, neutral throughout, no AI self-reference, no editorializing. Every paragraph attributes its claims to a named outlet.

I personally decompressed and read all four committed snapshots. source-0.html.gz (TechCrunch): confirms fleet of 105 vehicles, June 20 incident with heavy smoke obscuring an active emergency fire scene 'not cordoned off with cones', 'Nobody was on board', 'not aware of injuries', July 17 2026 report date (Sean O'Kane), and the verbatim location non-disclosure quote 'The NHTSA's report doesn't state where the June incident took place, and Zoox declined to say.' The NHTSA campaign number 26E044000 is genuinely supported: it appears in the source's embedded NHTSA recall hyperlink (href https://www.nhtsa.gov/?nhtsaId=26E044000) in BOTH TechCrunch and Engadget, so the attribution 'campaign number 26E044000, according to TechCrunch' is accurate. source-1.html.gz (Engadget): verbatim quotes confirmed — 'The Zoox vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop', 'under a teleguidance tactician's guidance, reversed', 'placed traffic cones at the scene blocking two of the three through-lanes', and the May 2025 Las Vegas passenger-car collision recall. source-2.html.gz (Gizmodo): verbatim 'may fail to properly detect and respond to heavy smoke', the full Zoox spokesperson root-cause quote ('detecting active EV scenes ... heavy smoke in certain situations'), the free-rides-in-Las-Vegas-and-San-Francisco / testing-in-Austin-and-Miami context, and the earlier-recalls list (hard braking, lane crossing, failing to predict movement of nearby cars). source-3.html.gz (Futurism): confirms the Amazon-owned framing and 'entire fleet of 105 autonomous robotaxis'. The one claim I could NOT verify in any source (0 occurrences across all four raw snapshots): the phrase 'over-the-air'.

All specifics verified against sources except the 'over-the-air' delivery descriptor. Fleet size (105), incident date (June 20), report date (July 17), the NHTSA campaign number, all direct quotes, and the prior-recall history are accurate. Critically, the article does NOT assert a location for the June 20 incident — it explicitly states neither the company nor the regulator disclosed where it occurred and quotes TechCrunch to that effect. The Las Vegas references are correctly scoped to (a) Zoox's general operations and (b) the separate May 2025 collision recall, neither of which is the June smoke incident. No aggregator 'Las Vegas' error is repeated.

Substantively accurate, well-sourced, neutral News piece. The single recoverable issue (the unsupported 'over-the-air' characterization attributed to TechCrunch) is honestly covered by a corrections record, so the article publishes under APPROVE_WITH_CORRECTIONS rather than being rejected.