{
 "schema_version": "0.4",
 "id": "REG-0002",
 "title": "Zoox robotaxi enters a smoke-obscured fire scene and reverses under remote guidance; software recall, June to July 2026",
 "batch": "B0",
 "family": "physical",
 "context": {
  "domain": "Autonomous vehicle (driverless robotaxi)",
  "autonomy_level": "alone",
  "actor_type": "Physical: Zoox purpose-built robotaxi",
  "actors": {
   "count": 1,
   "text": "1 (plus a remote teleguidance tactician)",
   "roles": [
    "defender"
   ]
  },
  "mandate_context": "production",
  "jurisdiction": [
   "United States (federal NHTSA, location not disclosed)"
  ],
  "autonomy_level_text": "Machine acts alone (no occupant), remote assistance available",
  "mandate_context_text": "Production service"
 },
 "provenance_tier": "public_regulatory",
 "status": "confirmed",
 "fields": [
  {
   "layer": "Mandate",
   "facet": "principal",
   "value": "Zoox, operating a driverless service",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Mandate",
   "facet": "objective",
   "value": "Navigate public roads without an occupant",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Actor",
   "facet": null,
   "value": "A Zoox robotaxi with no one on board",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Inputs",
   "facet": null,
   "value": "On 20 June 2026 the vehicle encountered heavy smoke obscuring an active emergency fire scene that had not been cordoned off with cones",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Decision",
   "facet": null,
   "value": "Not disclosed; the filing describes behavior, not the planner's state",
   "assertion_type": "assertion",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "low",
   "disputed": false
  },
  {
   "layer": "Envelope",
   "facet": "constraints",
   "value": "An active fire scene, obscured by heavy smoke and not yet cordoned off with cones; the filing names the gap as the software's detection of and response to heavy smoke, leaves its cause field blank, and does not say whether the missing cones played a part",
   "assertion_type": "interpretation",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "medium",
   "disputed": false
  },
  {
   "layer": "Action",
   "facet": null,
   "value": "The vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Outcome",
   "facet": null,
   "value": "State: averted. Zoox identified no injuries. First responders placed cones after the vehicle reversed. As of July 2026.",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Evidence",
   "facet": "event",
   "value": "Zoox's own account in the recall report; Zoox told NHTSA this was the only event of its kind",
   "assertion_type": "assertion",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "medium",
   "disputed": false
  },
  {
   "layer": "Recovery",
   "facet": "automated fallback",
   "value": "After entering the scene, the vehicle braked hard while attempting to steer away and came to a stop; the filing does not say how far into the scene it went",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Recovery",
   "facet": "technical",
   "value": "Under a remote teleguidance tactician's guidance, the vehicle reversed, after which first responders placed traffic cones blocking two of the three through-lanes; the filing does not say whether the remote person drove the vehicle or guided its software",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Recovery",
   "facet": "accountability",
   "value": "Zoox notified NHTSA of the event on 25 June 2026 under its Automated Vehicle Exemption Program obligation, investigated root cause between 22 June and 8 July, and discussed severity, frequency and root causes with NHTSA; its Safety Committee decided on 7 July 2026 to file a voluntary software recall covering 105 vehicles (manufacturer's report date 8 July in NHTSA's acknowledgment letter; Part 573 report submitted 16 July). As an interim remedy Zoox bolstered its existing operational measures to avoid driving near active fire emergency scenes and released updated software to the affected vehicles on 15 July 2026",
   "assertion_type": "fact",
   "source_ids": [
    "TC-ZOOX",
    "NHTSA-RCAK"
   ],
   "confidence": "high",
   "disputed": false
  },
  {
   "layer": "Inputs",
   "facet": "world_state",
   "value": "NHTSA's administrator wrote to driverless developers on 8 July 2026 warning them about driving into emergency scenes and failing to respond to smoke, fire and cones",
   "assertion_type": "fact",
   "source_ids": [
    "NHTSA-LTR"
   ],
   "confidence": "high",
   "disputed": false
  }
 ],
 "controls": {
  "failed": [
   {
    "id": "C-I3",
    "note": "Heavy-smoke detection and response: per the recall, the software may not detect and respond to heavy smoke in certain situations, particularly in active emergency scenes; the scene had not been cordoned off with cones",
    "confidence": "high",
    "basis": "curated"
   }
  ],
  "succeeded": [
   {
    "id": "C-R2",
    "note": "Safe stop",
    "confidence": "high",
    "basis": "curated"
   },
   {
    "id": "C-R3",
    "note": "Remote teleguidance: the vehicle reversed under a teleguidance tactician's guidance; no timing is disclosed, and the filing does not say whether the person took over driving",
    "confidence": "medium",
    "basis": "curated"
   },
   {
    "id": "C-R4",
    "note": "Voluntary recall process",
    "confidence": "high",
    "basis": "curated"
   }
  ],
  "absent": []
 },
 "applicable_rules": [
  "NHTSA Automated Vehicle Exemption Program reporting obligation (Zoox notified NHTSA of the event on 25 June 2026)",
  "Part 573 safety recall process"
 ],
 "unmapped": [],
 "corrections": [
  {
   "date": "2026-10-13",
   "field": "controls.C-I3",
   "old": "failed: Scene recognition without cones; absent: Smoke-specific perception handling (per the recall)",
   "new": "failed: Scene recognition without cones; Smoke-specific perception handling (per the recall) (absent)",
   "reason": "a control has one state per case; entries in two states merged into the state the record supports"
  },
  {
   "date": "2026-10-13",
   "field": "context.jurisdiction",
   "old": "United States (federal NHTSA | location not disclosed)",
   "new": "United States (federal NHTSA, location not disclosed)",
   "reason": "jurisdiction text was split at a comma inside parentheses"
  },
  {
   "date": "2026-10-13",
   "field": "fields and sources",
   "old": "recall 'filed on 7 July 2026'; 'first responders delayed in placing cones'; NHTSA letter 'a week earlier'; both sources cited via TechCrunch",
   "new": "recall decided 7 July, defect report dated 8 July, from the recall report linked directly; cones wording as the report states it; NHTSA letter linked and dated",
   "reason": "claims aligned to what each linked record says, found on review"
  },
  {
   "date": "2026-10-14",
   "field": "reviewed_by",
   "old": "none",
   "new": "Saurabh Bhatnagar (editor)",
   "reason": "case checked by the editor against its linked records"
  },
  {
   "date": "2026-10-14",
   "field": "named_parties[Zoox].right_of_reply",
   "old": "{\"offered\": null, \"response\": null}",
   "new": "{\"offered\": \"2026-10-14\", \"response\": null}",
   "reason": "right of reply offered by email from register@secureautonomous.com to press@zoox.com on 14 October 2026 (confirmed in the Sent folder); recorded at the editor's instruction"
  },
  {
   "date": "2026-10-16",
   "field": "inference.value",
   "old": "The successful control here was the remote human, not the stack; the recall is the stack catching up to what the human did",
   "new": "The control that worked here was the remote human, not the driving software. The recall brought the software up to what the human did.",
   "reason": "Reworded for readers before the editor's sign-off, after an outside review found it read as internal notes; the interpretation itself is unchanged"
  },
  {
   "date": "2026-10-20",
   "field": "title",
   "old": "Zoox robotaxi enters a smoke-obscured fire scene; teleoperator reverses it; software recall, June to July 2026",
   "new": "Zoox robotaxi enters a smoke-obscured fire scene and reverses under remote guidance; software recall, June to July 2026",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: Zoox's Part 573 recall report (TC-ZOOX) says the vehicle, \"under a teleguidance tactician's guidance, reversed\"; it does not say a remote human drove the vehicle, so 'teleoperator reverses it' overstated the record."
  },
  {
   "date": "2026-10-20",
   "field": "context.actors.text",
   "old": "1 (plus remote teleoperator)",
   "new": "1 (plus a remote teleguidance tactician)",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) names the remote person as a \"teleguidance tactician\" who guided the vehicle, not a teleoperator driving it."
  },
  {
   "date": "2026-10-20",
   "field": "applicable_rules",
   "old": "[\"NHTSA Standing General Order (crash and incident reporting)\", \"Part 573 safety recall process\"]",
   "new": "[\"NHTSA Automated Vehicle Exemption Program reporting obligation (Zoox notified NHTSA of the event on 25 June 2026)\", \"Part 573 safety recall process\"]",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) says \"On June 25, 2026, Zoox notified NHTSA of the event pursuant to its obligation under the Automated Vehicle Exemption Program\"; neither cited source ties this event to the Standing General Order, and no crash was reported."
  },
  {
   "date": "2026-10-20",
   "field": "outcome.affected_parties",
   "old": "[\"first responders (delay)\"]",
   "new": "[\"first responders (the vehicle entered their scene; no injuries identified, no delay reported)\"]",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) records that the vehicle entered the scene and that \"No injuries were identified\"; its \"impede first responders\" is the general safety-risk statement, and no source read reports an actual delay to responders in this event."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Envelope constraints",
   "old": "An uncordoned emergency scene lies outside normal operating assumptions; no cones meant the vehicle's scene-recognition had nothing to key on",
   "new": "An active fire scene, obscured by heavy smoke and not yet cordoned off with cones; the filing names the gap as the software's detection of and response to heavy smoke, leaves its cause field blank, and does not say whether the missing cones played a part",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) describes the defect as \"the software may not detect and respond to heavy smoke, particularly in active emergency scenes\" and leaves \"Description of the cause\" blank; it does not say the vehicle's scene recognition keys on cones or that the scene lay outside its operating assumptions, so those readings were removed."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Action",
   "old": "The vehicle braked hard while attempting to steer away, then stopped",
   "new": "The vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) says \"The Zoox vehicle entered the scene, then braked hard while attempting to steer away before coming to a stop\"; the entry into the scene was missing from the action."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Recovery automated fallback",
   "old": "Hard braking and a stop: the vehicle did not drive through the scene",
   "new": "After entering the scene, the vehicle braked hard while attempting to steer away and came to a stop; the filing does not say how far into the scene it went",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) says the vehicle \"entered the scene\" before braking and stopping; it does not describe how far it went, so 'did not drive through the scene' went beyond the record."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Recovery technical",
   "old": "A Zoox teleoperator reversed the vehicle away, letting first responders place traffic cones",
   "new": "Under a remote teleguidance tactician's guidance, the vehicle reversed, after which first responders placed traffic cones blocking two of the three through-lanes; the filing does not say whether the remote person drove the vehicle or guided its software",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) says \"The Zoox vehicle, under a teleguidance tactician's guidance, reversed, after which the first responders placed traffic cones at the scene blocking two of the three through-lanes\"; it does not say a teleoperator drove the vehicle."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Recovery accountability",
   "old": "Zoox investigated root cause and discussed severity, frequency and root causes with NHTSA; its Safety Committee decided on 7 July 2026 to file a voluntary software recall (defect report dated 8 July, covering 105 vehicles)",
   "new": "Zoox notified NHTSA of the event on 25 June 2026 under its Automated Vehicle Exemption Program obligation, investigated root cause between 22 June and 8 July, and discussed severity, frequency and root causes with NHTSA; its Safety Committee decided on 7 July 2026 to file a voluntary software recall covering 105 vehicles (manufacturer's report date 8 July in NHTSA's acknowledgment letter; Part 573 report submitted 16 July). As an interim remedy Zoox bolstered its existing operational measures to avoid driving near active fire emergency scenes and released updated software to the affected vehicles on 15 July 2026",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the 8 July date is not in the cited recall report (TC-ZOOX), which shows \"Submission Date: Jul 16, 2026\"; it is the \"Mfr's Report Date: July 08, 2026\" in NHTSA's acknowledgment letter (NHTSA-RCAK, now cited). TC-ZOOX also records the 25 June notification under the Automated Vehicle Exemption Program, the interim measures and the 15 July software release, which were missing."
  },
  {
   "date": "2026-10-20",
   "field": "fields.Recovery accountability.source_ids",
   "old": "[\"TC-ZOOX\"]",
   "new": "[\"TC-ZOOX\", \"NHTSA-RCAK\"]",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: NHTSA's acknowledgment letter for recall 26E044 (NHTSA-RCAK) is the record that carries the 8 July manufacturer's report date."
  },
  {
   "date": "2026-10-20",
   "field": "controls.C-I3",
   "old": "{\"note\": \"Scene recognition without cones; Smoke-specific perception handling (per the recall) (absent)\", \"confidence\": \"high\"}",
   "new": "{\"note\": \"Heavy-smoke detection and response: per the recall, the software may not detect and respond to heavy smoke in certain situations, particularly in active emergency scenes; the scene had not been cordoned off with cones\", \"confidence\": \"high\"}",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) names the gap as detecting and responding to heavy smoke and says the software update \"enhances existing capability\"; it does not say scene recognition depends on cones or that smoke handling was absent."
  },
  {
   "date": "2026-10-20",
   "field": "controls.C-R3",
   "old": "{\"note\": \"Teleoperation\", \"confidence\": \"high\"}",
   "new": "{\"note\": \"Remote teleguidance: the vehicle reversed under a teleguidance tactician's guidance; no timing is disclosed, and the filing does not say whether the person took over driving\", \"confidence\": \"medium\"}",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) says only that the vehicle reversed \"under a teleguidance tactician's guidance\"; no source gives the timing or says the remote person took over driving, so the mapping to human takeover with a time window is held at medium confidence pending the editor's classification."
  },
  {
   "date": "2026-10-20",
   "field": "inference.value",
   "old": "The control that worked here was the remote human, not the driving software. The recall brought the software up to what the human did.",
   "new": "Two responses appear in the recall filing, one after the other: after entering the smoke-obscured scene, the vehicle braked hard while trying to steer away and stopped; it then reversed under a remote teleguidance tactician's guidance, after which first responders placed cones. The filing ties the event to software that in certain situations may not detect and respond to heavy smoke, and the update enhances that detection and response. The record does not show why the vehicle entered the scene (the cause field is blank), whether the remote person drove the vehicle or guided its software, or whether the update changes what the vehicle does once inside such a scene.",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the recall report (TC-ZOOX) shows the vehicle itself braked and stopped before any remote guidance is mentioned, and that the reversal happened \"under a teleguidance tactician's guidance\" without saying the person drove; the software update \"enhances existing capability of detecting and responding to heavy smoke\" and nothing in it says the vehicle would now reverse itself out, so 'the control that worked was the remote human, not the driving software' and 'the recall brought the software up to what the human did' went beyond the record. The interpretation was not signed (signed_by null); the editor must sign the new wording."
  },
  {
   "date": "2026-10-20",
   "field": "sources.TC-ZOOX",
   "old": "{\"title\": \"Zoox, Inc., Part 573 Safety Recall Report 26E044: ADS software may fail to detect and respond to heavy smoke (105 vehicles)\", \"type\": \"regulator\", \"checked\": \"2026-10-13\"}",
   "new": "{\"title\": \"Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles)\", \"type\": \"company\", \"checked\": \"2026-10-20\"}",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: the report is Zoox's own submission (\"Manufacturer Name: Zoox, Inc.\", \"submitted pursuant to 49 CFR § 573\") published on NHTSA's site, so its type is company, not regulator (tier public_regulatory kept); the subtitle used the subject line of NHTSA's acknowledgment letter and now uses the report's own defect description, \"the software may not detect and respond to heavy smoke\"."
  },
  {
   "date": "2026-10-20",
   "field": "sources.NHTSA-RCAK",
   "old": null,
   "new": "{\"title\": \"NHTSA Office of Defects Investigation, Recall Management Division, recall acknowledgment letter to Zoox, Inc., 26E044: ADS [automated driving system] Software May Fail to Detect and Respond to Heavy Smoke\", \"type\": \"regulator\", \"url\": \"https://static.nhtsa.gov/odi/rcl/2026/RCAK-26E044-8851.pdf\", \"via_press\": false, \"date\": \"2026-07-16\", \"tier\": \"public_regulatory\", \"interest\": null, \"primary\": true, \"checked\": \"2026-10-20\"}",
   "reason": "Found in the editor's source re-check of 19-20 October 2026: NHTSA's acknowledgment letter for recall 26E044, dated July 16, 2026, gives \"Mfr's Report Date: July 08, 2026\" and \"Potential Number of Units Affected: 105\"; added as the primary record for the 8 July date."
  },
  {
   "date": "2026-10-21",
   "field": "inference.value",
   "old": "Two responses appear in the recall filing, one after the other: after entering the smoke-obscured scene, the vehicle braked hard while trying to steer away and stopped; it then reversed under a remote teleguidance tactician's guidance, after which first responders placed cones. The filing ties the event to software that in certain situations may not detect and respond to heavy smoke, and the update enhances that detection and response. The record does not show why the vehicle entered the scene (the cause field is blank), whether the remote person drove the vehicle or guided its software, or whether the update changes what the vehicle does once inside such a scene.",
   "new": "Two responses appear in the recall filing, one after the other: after entering the smoke-obscured scene, the vehicle braked hard while trying to steer away and stopped; it then reversed under a remote teleguidance tactician's guidance, after which first responders placed cones. The filing ties the event to software that in certain situations may not detect and respond to heavy smoke, and the update enhances that detection and response. The record gives no root cause for this event (the filing's cause field is blank, and the National Highway Traffic Safety Administration's acknowledgment describes the defect only in general terms, as software that 'may fail to detect heavy smoke, allowing the vehicle to enter an area of low visibility'), and does not show whether the remote person drove the vehicle or guided its software, or whether the update changes what the vehicle does once inside such a scene.",
   "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: the regulator's acknowledgment letter (NHTSA-RCAK) does describe, in general terms, why such a vehicle could enter the scene; what the record lacks is a root cause for this event."
  },
  {
   "date": "2026-10-21",
   "field": "inference.source_ids",
   "old": "[\"TC-ZOOX\"]",
   "new": "[\"TC-ZOOX\", \"NHTSA-RCAK\"]",
   "reason": "Found in the editor's second, independent check of the interpretations, 21 October 2026: the interpretation now quotes the regulator's acknowledgment letter."
  },
  {
   "date": "2026-10-21",
   "field": "inference.signed_by",
   "old": "Saurabh Bhatnagar",
   "new": null,
   "reason": "The interpretation's wording changed after the editor signed it (second, independent check of 21 October 2026); the signature is cleared so the editor signs the corrected wording."
  },
  {
   "date": "2026-10-28",
   "field": "named_parties[Zoox].right_of_reply",
   "old": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [], \"note\": \"no correction since the offer adds or worsens a claim about this party in words that are not its own\"}]}",
   "new": "{\"offered\": \"2026-10-14\", \"response\": null, \"assessed_through\": \"2026-10-22\", \"assessments\": [{\"through\": \"2026-10-22\", \"date\": \"2026-10-22\", \"by\": \"editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering\", \"triggered\": [], \"note\": \"no correction since the offer adds or worsens a claim about this party in words that are not its own\"}], \"no_response_as_of\": \"2026-10-28\"}",
   "reason": "right of reply recorded by a human"
  }
 ],
 "created": "2026-10-05",
 "last_reviewed": "2026-10-28",
 "actor_status": "confirmed",
 "provenance_tier_text": "Public and regulatory",
 "status_text": "Confirmed",
 "outcome": {
  "state": "averted_by_control",
  "severity": "none",
  "affected_parties": [
   "first responders (the vehicle entered their scene; no injuries identified, no delay reported)"
  ],
  "cost": "none reported",
  "regime_consequence": "voluntary software recall",
  "as_of": "July 2026",
  "derived_by": "backfill-curated"
 },
 "inference": {
  "value": "Two responses appear in the recall filing, one after the other: after entering the smoke-obscured scene, the vehicle braked hard while trying to steer away and stopped; it then reversed under a remote teleguidance tactician's guidance, after which first responders placed cones. The filing ties the event to software that in certain situations may not detect and respond to heavy smoke, and the update enhances that detection and response. The record gives no root cause for this event (the filing's cause field is blank, and the National Highway Traffic Safety Administration's acknowledgment describes the defect only in general terms, as software that 'may fail to detect heavy smoke, allowing the vehicle to enter an area of low visibility'), and does not show whether the remote person drove the vehicle or guided its software, or whether the update changes what the vehicle does once inside such a scene.",
  "source_ids": [
   "TC-ZOOX",
   "NHTSA-RCAK"
  ],
  "confidence": "medium",
  "signed_by": "Saurabh Bhatnagar",
  "signed_on": "2026-10-21"
 },
 "named_parties": [
  {
   "name": "Zoox",
   "right_of_reply": {
    "offered": "2026-10-14",
    "response": null,
    "assessed_through": "2026-10-22",
    "assessments": [
     {
      "through": "2026-10-22",
      "date": "2026-10-22",
      "by": "editor's call of 22 October 2026 on the rule 19 review by four independent agents (reports rule19_1 to rule19_4); GitHub (REG-0005) judged borderline and not triggering",
      "triggered": [],
      "note": "no correction since the offer adds or worsens a claim about this party in words that are not its own"
     }
    ],
    "no_response_as_of": "2026-10-28"
   }
  }
 ],
 "sources": {
  "NHTSA-LTR": {
   "title": "NHTSA Administrator Jonathan Morrison, letter to developers of driverless automated driving systems on interactions with first responders, 8 Jul 2026",
   "type": "regulator",
   "url": "https://www.nhtsa.gov/sites/nhtsa.gov/files/2026-07/ADS-developers-letter-july-2026.pdf",
   "via_press": false,
   "date": "2026-07-08",
   "tier": "public_regulatory",
   "interest": null,
   "primary": true,
   "checked": "2026-10-13"
  },
  "TC-ZOOX": {
   "title": "Zoox, Inc., Part 573 Safety Recall Report 26E044 (Zoox's own filing, published by NHTSA): software may not detect and respond to heavy smoke (105 vehicles)",
   "type": "company",
   "url": "https://static.nhtsa.gov/odi/rcl/2026/RCLRPT-26E044-2993.pdf",
   "via_press": false,
   "date": "2026-07-16",
   "tier": "public_regulatory",
   "interest": null,
   "primary": true,
   "checked": "2026-10-20"
  },
  "NHTSA-RCAK": {
   "title": "NHTSA Office of Defects Investigation, Recall Management Division, recall acknowledgment letter to Zoox, Inc., 26E044: ADS [automated driving system] Software May Fail to Detect and Respond to Heavy Smoke",
   "type": "regulator",
   "url": "https://static.nhtsa.gov/odi/rcl/2026/RCAK-26E044-8851.pdf",
   "via_press": false,
   "date": "2026-07-16",
   "tier": "public_regulatory",
   "interest": null,
   "primary": true,
   "checked": "2026-10-20"
  }
 },
 "derived_by": "backfill-curated",
 "reviewed_by": "Saurabh Bhatnagar (editor)"
}