"Fixed in the update" is a claim, not evidence: notes on Waymo's freeway recalls and an AI-citation ruling A review of two 20 November 2026 events — Waymo's recall of robotaxis that drove into closed freeway lanes and a Kansas Court of Appeals ruling against a self-represented litigant whose AI-drafted filings cited nonexistent cases — found that provenance logging cannot establish whether a fix or a citation is actually correct. The analysis, registered as cases V1111WAYMOFREEWAY and V1120LINGLE under the VAP provenance framework, notes that VAP's automotive profile remains "Planned" with no specification, so no robotaxi fleet can claim conformance, and that the appellate court imposed no new sanctions, instead disregarding fabricated authority and warning future filers that self-represented litigants share an attorney's duty to verify AI output. Two things happened on 20 November 2026 that look unrelated. Waymo announced two recalls after its robotaxis drove into closed freeway lanes. And the Kansas Court of Appeals published an opinion about a self-represented litigant whose AI-drafted filings cited cases that do not exist. A monitoring brief sent to VSO, which maintains the VAP provenance framework, bundled them together and presented provenance logging as the fix for both. We checked the claims against the primary sources and registered both cases V1111WAYMOFREEWAY and V1120LINGLE . The brief was wrong in a way that is useful for anyone who builds systems that log decisions. Here is what the sources say, and what logging can and cannot do in each case. The timeline matters, and the brief had it backwards. The DMV's condition for lifting the restriction is that Waymo "demonstrates" its corrective actions are effective. That is the engineering problem worth noticing. "Fixed in version X" is a claim. Turning it into evidence takes, at minimum: A tamper-evident, externally anchored log helps with the second point in a specific, limited way. A third party can check that anchored records were not altered afterwards, and can detect events omitted after anchoring at batch granularity within a declared scope. In VAP v1.2 that is the Completeness Invariant, INT-008. It cannot tell you whether the fix was adequate. It cannot recover an event the vehicle never recorded. And it does not cover events that were never put into an anchored batch at all. There is also a scope fact: VAP's automotive profile, DVP, is listed as "Planned" in the v1.2 registry, which means no specification document exists. Since a deployment must sit under exactly one domain profile §4.6.3, rule 1 , nobody can claim VAP conformance for a robotaxi fleet today. In Lingle v. Subaru of Wichita No. 129,581 , the district court had warned the litigant several times to verify sources in motions it called "admittedly Artificial Intelligence-generated." It then sanctioned him in several separate awards. The brief said the appellate court imposed about $1,480 in sanctions. That was one of the district court's awards. The appellate court imposed no new sanction. It checked the appellate brief itself and found cases and statutory subsections that do not exist, plus 36 misstatements of 11 real holdings. It disregarded the fabricated authority, affirmed, and warned future filers. Its syllabus: a self-represented litigant has the same duty as an attorney to verify AI output. If you build LLM features, the lesson is old but keeps getting relearned. A perfect record of how text was generated tells you nothing about whether the text is true. You could sign every prompt and every token, and a fabricated case citation would still be fabricated, just with a better audit trail. The check that caught these errors was a lookup against an authoritative source: the court reading each citation against the reporters and statutes. If your product emits citations, the verification step belongs in the pipeline, before the output reaches a user or a court. VAP's own normative text says this. Conformance "does not warrant the correctness, fairness, or safety of the underlying AI decisions — only the integrity, completeness at anchor granularity , and attributability of their records" §1.6 c . VSO develops VAP. Zero external implementations of VAP and zero Evidence Packs accepted in any proceeding disclosure reviewed 11 November 2026; count dated 25 October 2026 . A contract figure published earlier was withdrawn on 24 October 2026; the withdrawal does not mean the count is zero, and no contract, customer or revenue figure is asserted. VAP v1.2.0 is a draft with no standing in any established standards body. This post was researched and drafted with Claude Anthropic , which is not a party to either case. Full analysis on Medium: https://medium.com/@veritaschain/two-questions-a-record-cannot-answer-4d3b4ed5ce99 https://medium.com/@veritaschain/two-questions-a-record-cannot-answer-4d3b4ed5ce99 Sources: Reuters via syndication https://lufkindailynews.com/news reuters/business/waymo-recalls-self-driving-cars-over-closed-freeway-lanes-manual-traffic-control/article 593166c1-4a30-50c7-bc02-716dfa175776.html · TechCrunch https://techcrunch.com/2026/11/17/waymo-suspends-freeway-rides-nationwide-after-california-dmv-order/ · AP via KPBS https://www.kpbs.org/news/quality-of-life/2026/11/17/california-bans-waymo-autonomous-vehicles-from-state-freeways-saying-they-pose-an-imminent-hazard · NHTSA 26E035 https://static.nhtsa.gov/odi/rcl/2026/RCLRPT-26E035-7637.pdf · Lingle v. Subaru of Wichita https://www.courtlistener.com/opinion/11067771/lingle-v-subaru-of-wichita/ · VSO incident registry https://veritaschain.org/incidents/ · VAP v1.2 spec https://github.com/veritaschain/vap-spec/blob/main/spec/v1.2/VAP Framework Specification.md