You will be provided with a research report. The body of the report will contain some citations to references.

Citations in the main text may appear in the following forms:
1. A segment of text + space + number, for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels 15"
2. A segment of text + [number], for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels[15]"
3. A segment of text + [number†(some line numbers, etc.)], for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels[15†L10][5L23][7†summary]"
4. [Citation Source](Citation Link), for example: "According to [ChinaFile: A Guide to Social Class in Modern China](https://www.chinafile.com/reporting-opinion/media/guide-social-class-modern-china)'s classification, Chinese society can be divided into nine strata"

Please identify **all** instances where references are cited in the main text, and extract (fact, ref_idx, url) triplets. When extracting, pay attention to the following:
1. Since these facts will need to be verified later, you may need to look for some context before and after the citation to ensure that the fact is complete and understandable, rather than just a simple phrase or short expression.
2. If a fact cites multiple references, then it should correspond to two triplets: (fact, ref_idx_1, url_1) and (fact, ref_idx_2, url_2).
3. For the third form of citation (i.e., where the citation source and link appear directly in the text), the ref_idx should be uniformly set to 0.
4. If the main text does not specify the exact location of the citation (for example, only the reference list is listed at the end of the article, without specifying the citation point in the text), please return an empty list.

You should return a JSON list format, where each item in the list is a triplet, for example:
[
    {
        "fact": "Text segment from the original document. Note that Chinese quotation marks should use full-width marks. And add a single backslash before the English quotation mark to make it a readable for python json module.",
        "ref_idx": "The index of the cited reference in the reference list for this text segment.",
        "url": "The URL of the cited reference for this text segment (extracted from the reference list at the end of the research report or from the parentheses at the citation point)."
    }
]

Here is the main text of the research report:
# Systemic Liability Allocation in Shared Human-Machine Driving Contexts: A Socio-Technical, Jurisprudential, and Regulatory Framework

## Technical Architecture and the Socio-Technical Dynamics of Shared Control

The commercial deployment of advanced driver-assistance systems (ADAS) has fundamentally disrupted the traditional legal paradigm of vehicular negligence, which historically presumed a unified, continuous locus of human agency behind the wheel [1]. Modern vehicles operate increasingly within a regime of shared control, an intermediate state between full human manual operation and complete automated autonomy [2]. This technological transition creates an acute socio-technical tension: automated sub-systems physically actuate lateral and longitudinal controls while statutory and common-law regimes continue to treat the human occupant as the primary dynamic operator who is strictly accountable for collision avoidance [2]. Understanding the legal viability of this allocation requires an examination of the automated driving system's operational architecture and the cognitive limits of human supervision [2].

### SAE Automation Taxonomies and the Dynamic Driving Task

The Society of Automotive Engineers (SAE) International standard J3016 establishes the primary technical and taxonomy baseline referenced by automotive engineers, federal regulators, and state legislatures [4]. Standard J3016 partitions vehicular automation into six discrete tiers, delineated by how the Dynamic Driving Task (DDT) and the DDT fallback are distributed between the human operator and the automated driving system [4]. The DDT encompasses the complete array of real-time operational and tactical functions required to operate a motor vehicle in traffic: operational actuation (steering, braking, accelerating), tactical maneuvering (path planning, object avoidance, turn signaling), and visual-auditory environmental scanning (Object and Event Detection and Response, or OEDR) [5].

| SAE Level | Classification | Lateral and Longitudinal Actuation | Object and Event Detection and Response (OEDR) | Dynamic Driving Task (DDT) Fallback | Operational Design Domain (ODD) | Legal Presumption of Operator Status |
| --- | --- | --- | --- | --- | --- | --- |
| **Level 0** | No Driving Automation | Human Driver | Human Driver | Human Driver | Unlimited | Full Dynamic Operator |
| **Level 1** | Driver Assistance | System executes either lateral (e.g., LKA) or longitudinal (e.g., ACC) actuation | Human Driver | Human Driver | Limited | Full Dynamic Operator |
| **Level 2** | Partial Driving Automation | System executes simultaneous lateral and longitudinal actuation | Shared (System detects discrete targets; human continuously supervises) | Human Driver | Limited (Highway, marked arterials) | Sole Dynamic Operator; Primary Fault Locus |
| **Level 3** | Conditional Driving Automation | System executes simultaneous lateral and longitudinal actuation | System executes complete OEDR within active domain | Human Fallback User-in-Charge (resumes control upon request) | Strictly Limited (e.g., traffic jam pilot \(\le 60\text{ km/h}\)) | Conditional Passenger / Re-engaged Fallback Operator |
| **Level 4** | High Driving Automation | System executes simultaneous lateral and longitudinal actuation | System executes complete OEDR within active domain | System (Automated execution of Minimum Risk Maneuver) | Geofenced / Environmental limits | Pure Passenger; System Entity Liable |
| **Level 5** | Full Driving Automation | System executes simultaneous lateral and longitudinal actuation | System executes complete OEDR across all operational settings | System (Automated execution of Minimum Risk Maneuver) | Unlimited | Pure Passenger; System Entity Liable |

In an SAE Level 2 configuration—encompassing consumer platforms such as Tesla Autopilot, General Motors Super Cruise, and Ford BlueCruise—the system performs lateral path-centering and longitudinal speed-spacing simultaneously [5].

However, SAE Level 2 architecture delegates OEDR supervision and DDT fallback entirely to the human driver [4]. The human must continually scan the operational environment, evaluate downstream spatial hazards, and retain psychomotor readiness to intervene instantaneously [5].

Conversely, an SAE Level 3 system—such as Mercedes-Benz Drive Pilot—assumes full operational control and environmental monitoring within a defined Operational Design Domain (ODD), relieving the human occupant of continuous tactical surveillance [6].

The critical division between Level 2 and Level 3 centers on the DDT fallback: Level 2 legally and mechanically requires continuous, unprompted human supervision, whereas Level 3 permits secondary task immersion until the system issues a structured Transition Demand [6].

### Cognitive Ergonomics: Automation Complacency, Bias, and Out-of-the-Loop Deficits

The engineering assumption underlying Level 2 shared control—that an untrained human can remain visually and cognitively vigilant while a machine executes physical vehicle stabilization—conflicts directly with human factors engineering and cognitive ergonomics [2]. When an ADAS demonstrates high functional reliability over long stretches of highway transit, the operator experiences automation complacency, characterized by a rapid decline in visual sampling and situational monitoring [2]. Complementing complacency is automation bias, the cognitive heuristic whereby humans uncritically trust algorithmic outputs and assume that the absence of a machine alert confirms the absence of physical hazard [2].

This behavioral pattern leads directly to the out-of-the-loop (OOTL) performance deficit [11]. By removing physical motor control and tactile steering feedback, the ADAS severs the driver's sensorimotor integration, producing an acute decay in situational awareness [2]. A disengaged human supervisor required to intervene during an automated failure cannot re-enter the operational control loop instantaneously [5]. The cognitive latency required to transition from secondary task immersion to manual intervention is governed by sequential psychophysiological stages:

\[t_{\text{takeover}} = t_{\text{detection}} + t_{\text{perception}} + t_{\text{comprehension}} + t_{\text{decision}} + t_{\text{action}}\]

Empirical investigations show that while simple mechanical repositioning of the hands on the steering wheel can occur within \(1.5\) to \(2.5\) seconds, the higher-order visual comprehension and spatial orientation necessary to navigate an evolving emergency typically requires between \(5.0\) and \(10.0\) seconds [5].

Because highway-speed emergencies typically unfold within a window of \(1.5\) to \(3.0\) seconds, an out-of-the-loop driver cannot execute effective crash avoidance [5].

The architecture of shared control thus creates a structural contradiction: it designs the human out of active physical operations while relying entirely on immediate human cognitive intervention to resolve system-level corner cases [2].

### Perceptual Modalities, Sensor Physics, and the Edge-Case Problem

The automated perception stack combines multiple sensor modalities—primarily optical cameras, millimeter-wave radar, and occasionally LiDAR—operating alongside algorithmic interpretation pipelines [6]. Each modality is constrained by underlying physical limitations:

- Optical cameras rely on ambient light and clear optical sightlines, leaving them vulnerable to direct solar flare, dense atmospheric fog, heavy precipitation, and high-contrast shadow boundaries [5].
- Millimeter-wave radar resolves range and relative closing velocities effectively through adverse weather, but radar signal-processing software typically filters out static, unmoving radar returns to prevent false-positive emergency braking on stationary overhead highway signs and bridges [5].
- Ultrasonic sensors provide short-range proximity detection (\(<5\text{ meters}\)) suitable for low-speed parking, but cannot support high-speed tactical monitoring.
- LiDAR constructs dense 3D point clouds with spatial precision, but its commercial deployment remains limited by hardware costs, physical packaging requirements, and signal attenuation in severe weather conditions [6].

These sensors feed machine-learning neural networks trained on specific object taxonomies [17]. When confronted with out-of-distribution artifacts—such as an overturned white trailer crossing a travel lane, a highway crash attenuator whose geometry has been altered by a prior strike, or emergency vehicles parked diagonally across highway shoulders with non-standard flashing light patterns—the automated perception engine frequently experiences classification failures [5].

Because the filtering algorithms discard these unclassified obstacles as background noise, the longitudinal control subsystem maintains throttle velocity, navigating into stationary obstacles without issuing an automated brake command or activating a takeover request [5].

If the vehicle lacks an active closed-loop driver monitoring system capable of measuring eye gaze, the driver remains unaware of the impending collision until impact is unavoidable [4].

## Judicial and Statutory Paradigms in Tort and Products Liability

The civil litigation arising from ADAS-involved collisions exposes deep structural gaps between traditional tort principles and shared automated driving [2]. Courts must apportion liability across two competing fault axes: the driver’s duty of care under common-law negligence, and the manufacturer’s product liability under design defect, marketing defect, and manufacturing defect theories [18].

### The Driver Duty of Care and the Fiction of Continuous Vigilance

At common law, the operator of a motor vehicle owes a duty to exercise reasonable care to avoid causing injury to other roadway users and vehicle passengers [18]. This duty requires maintaining an alert visual lookout, traveling at speeds appropriate for road conditions, yielding right-of-way, and taking reasonable evasive action when hazards appear [18]. In civil ADAS litigation, automotive manufacturers use this common-law framework to construct a defense based on sole proximate cause and intervening, superseding causation [18].

The defense argues that because the owner’s manual, visual disclaimers, and user software agreements specify that Level 2 automation requires continuous human supervision, any collision resulting from automated misclassification or control loss stems directly from the driver’s failure to maintain a visual lookout [18].

This legal strategy leverages the concept of the reasonable person, treating the human driver as an independent supervisory agent whose failure to intervene breaks the chain of proximate causation between an alleged software failure and the plaintiff's injuries [18].

However, this legal posture relies on an empirical assumption that human-factors research has consistently challenged: it expects an operator to maintain continuous mental vigilance over a repetitive, machine-executed task [4].

While tort doctrine accounts for distraction in conventional driving, civil courts presiding over ADAS lawsuits often hold human drivers strictly responsible for inattention, even when that inattention was invited by the vehicle's automated systems [5].

Consequently, trial juries often assign primary or complete fault to the human driver under comparative negligence rules, finding that an alert driver would have observed the physical obstacle in time to brake manually [5].

### Products Liability Doctrine Under the Restatement of Torts

To establish manufacturer liability in tort, plaintiffs bring claims under the Restatement (Second) of Torts § 402A or the Restatement (Third) of Torts: Products Liability § 2, asserting design defect, failure to warn, or manufacturing defect claims [19].

Under § 2(b) of the Restatement (Third), a product is defective in design when the foreseeable risks of harm could have been reduced or avoided through the adoption of a Reasonable Alternative Design (RAD), and the omission of that alternative renders the product not reasonably safe [6]. In ADAS design defect litigation, plaintiffs focus on the system’s driver engagement and monitoring architecture [5].

Plaintiffs argue that marketing an SAE Level 2 system that relies only on passive steering-wheel torque sensors—which measure mechanical resistance but cannot confirm visual attention—constitutes a defectively dangerous design [5].

The viable RAD presented in this litigation is a closed-loop, driver-facing infrared camera system capable of continuous optical eye-gaze and head-pose tracking, coupled with hard operational geofencing [5].

Because competing automotive manufacturers integrated driver-facing optical tracking and geofencing to limit automated steering to divided access-controlled freeways, plaintiffs can satisfy the risk-utility balancing test:

\[\text{Cost of Infrared Camera \& Geofencing Modules } (B) \ll \text{Probability of Inattentive Crash } (P) \times \text{Catastrophic Harm Magnitude } (L)\]

The engineering cost and operational burden of direct driver monitoring are minimal compared to the foreseeable probability and severity of high-speed collisions caused by driver complacency [5].

Under § 2(c) of the Restatement (Third), a product is defective due to inadequate instructions or warnings when foreseeable risks of harm could have been reduced or avoided by reasonable warnings, and their omission renders the product unsafe [22].

A central tenet of products liability law is that a manufacturer cannot cure a defective physical design merely by providing operational warnings or manual disclaimers where an economically and technologically feasible alternative design exists to eliminate the hazard [22].

Furthermore, a manufacturer’s scope of liability extends beyond intended operational uses to encompass all reasonably foreseeable misuses of the product [22].

This doctrine intersects directly with commercial marketing strategies known as "autonowashing" [2]. When manufacturers use brand names such as "Autopilot" or "Full Self-Driving," they generate consumer expectations that exceed the hardware's actual operational limits [8]. Plaintiffs argue that:

- Marketing campaigns and public executive statements overemphasize autonomous capabilities, fostering uncalibrated consumer trust [8].
- Fine-print warnings buried within complex digital user manuals asserting that "the driver must maintain control at all times" cannot serve as an absolute liability shield [18].
- Because human cognitive disengagement and automation complacency are known consequences of vehicular automation, driver inattention during automated steering constitutes foreseeable misuse rather than an extraordinary intervening act [5].

Under § 2(a) of the Restatement (Third), a manufacturing defect occurs when a specific physical product departs from its intended design specifications, even if the manufacturer exercised all possible care in fabrication and quality assurance [22].

In ADAS litigation, manufacturing defect claims rarely succeed because collision dynamics typically stem from systemic software logic or inherent sensor limitations shared across the vehicle fleet, rather than unique hardware anomalies [5].

However, actionable manufacturing claims can arise when a plaintiff demonstrates physical sensor assembly flaws, such as misaligned radar brackets, out-of-spec camera lens focal planes, or improper electronic transceiver calibrations that degrade object detection below the manufacturer's own engineering baselines [19].

### Contractual Exculpation and Informational Disclaimers

Automotive OEMs rely on terms-of-use agreements, infotainment system startup clicks, and extensive user-manual caveats requiring drivers to confirm their supervisory obligations before enabling ADAS features [18]. Under fundamental tort principles, contractual clauses that seek to disclaim, exculpate, or limit liability for personal physical injury caused by a defectively designed product are void as against public policy under Restatement (Third) § 18 and Uniform Commercial Code (UCC) § 2-719(3) [22].

While an OEM cannot enforce these provisions as express liability releases against an injured third party or vehicle passenger, disclaimers serve an important evidentiary purpose in defense litigation [18].

Defense counsel introduces signed terms of use and manual warnings to establish the driver's subjective awareness of system limitations [18].

This evidence helps OEMs argue comparative fault, establish assumption of the risk, or defeat reliance elements in fraud and negligent misrepresentation claims by showing that the operator knowingly operated the system outside its documented design parameters [18].

## Empirical Regulatory Findings and Jurisprudential Case Precedents

Administrative defect investigations and modern trial court dockets trace the evolving line of responsibility between machine defects and human error [5].

### Administrative Investigations: NHTSA ODI EA22-002 and SGO 2021-01

The interaction between ADAS design and operator disengagement was formally documented in the National Highway Traffic Safety Administration's (NHTSA) Office of Defects Investigation (ODI) Engineering Analysis **EA22-002**, which concluded in April 2024 [4]. The investigation examined 956 crashes involving vehicles with Autopilot or Full Self-Driving engaged, identifying 29 fatal collisions and hundreds of injuries [8].

| Crash Typology (EA22-002) | Case Count | Fatalities / Injuries | Key Operational Factors | Telemetric & Human Factors Findings |
| --- | --- | --- | --- | --- |
| **Frontal-Plane Collisions** | 211 crashes | 14 Fatalities / 49 Serious Injuries | Vehicle struck an obstacle or vehicle in its forward path, including stationary first responder vehicles [5]. | In 59 crashes with verified visibility metrics, hazards were visible for \(\ge 5\text{ seconds}\) prior to impact; in 19 crashes, visible for \(\ge 10\text{ seconds}\) without evasive steering or braking [5]. |
| **Yaw Loss of Control** | 53 crashes | Road departures and barrier strikes [5]. | System operated in low-traction environments (wet pavement, ice) outside manufacturer recommendations [4]. | Vehicle experienced immediate lateral loss of control following automated lane-centering failure [5]. |
| **Inadvertent Override** | 55 crashes | Single-vehicle roadway departure collisions [5]. | Driver manually steered out of lane, deactivating lateral autosteer while cruise control remained engaged [5]. | Drivers failed to recognize that lateral control had disengaged while longitudinal speed was maintained; crashes occurred \(<5\text{ seconds}\) post-override [5]. |

NHTSA concluded that the system suffered from a design defect: its driver-engagement monitoring was inadequate for the system's operational design domain and permissive capabilities [4].

By permitting automated operation on roadways with cross-traffic and intersections without direct gaze verification, the system fostered automation complacency and created a critical safety gap that led to foreseeable driver misuse [4].

This defect determination resulted in Safety Recall **23V838**, requiring over-the-air software updates to strengthen driver monitoring and warning prompts across more than two million vehicles, followed by Recall Query **RQ24009** to assess whether these software remedies sufficiently mitigated the underlying risk [5].

To address persistent underreporting and data gaps across the autonomous driving sector, NHTSA issued **Standing General Order (SGO) 2021-01**, requiring named manufacturers and fleet operators of SAE Level 2 ADAS and SAE Level 3–5 ADS to report crashes on public roads [31].

The order mandates crash notification within five days for any incident where an automated system was engaged within thirty seconds of an impact resulting in a fatality, hospital-treated injury, airbag deployment, vehicle tow-away, or collision with a vulnerable road user [32].

By establishing a 30-second reporting window, the SGO closed an evidentiary gap where manufacturers previously avoided automated crash reporting by asserting that software had automatically disengaged seconds or fractions of a second before impact [31].

### Civil Tort Litigation Precedents

Trial courts have delivered mixed outcomes in ADAS product liability claims, with juror verdicts often turning on whether the plaintiff's actions violated basic operating instructions [18].

| Case Style & Citation | Court & Jurisdiction | System & Platform | Alleged Defect & Legal Causes of Action | OEM Defense Strategy | Evidentiary Determinants & Disposition |
| --- | --- | --- | --- | --- | --- |
| ***Justine Hsu v. Tesla, Inc.*** (2023) [18] | Superior Court of California, Los Angeles County | Tesla Autopilot (2016 Model S) | Strict products liability, failure to warn, fraud; vehicle veered into a street median at 25–30 mph, deploying airbags and fracturing plaintiff's jaw [18]. | Operator misuse; use of highway feature on urban surface streets; driver inattention [18]. | **Defense Verdict:** Jury found the system performed as designed; warnings were adequate; telematics confirmed driver hands off wheel for \(\sim 90\text{ seconds}\) looking away [18]. |
| ***Micah Lee v. Tesla, Inc.*** (2023) [34] | Superior Court of California, Riverside County | Tesla Autopilot (2019 Model 3) | Strict products liability (design defect); uncommanded steering departure at 65 mph resulting in fatal tree impact and fire. | Driver intoxication; operator failure to maintain manual steering control; absence of hardware failure. | **Defense Verdict:** Jury cleared manufacturer of defect liability; attributed collision to driver error. |
| ***Estate of Walter Huang v. Tesla, Inc.*** (2024) [15] | Superior Court of California, Santa Clara County | Tesla Autopilot (2017 Model X) | Wrongful death, strict liability; vehicle steered toward highway gore and accelerated to 71 mph into concrete barrier [5]. | Contributory negligence; smartphone gaming distraction; failure to heed manual warnings [38]. | **Confidential Settlement:** Resolved prior to trial after court admitted NTSB findings and internal corporate communications regarding known perception flaws [37]. |
| ***Jeremy Banner v. Tesla, Inc.*** (2019–2024) [14] | Florida Circuit Court, Palm Beach County | Tesla Autopilot (2018 Model 3) | Strict products liability; perception system failed to detect semi-trailer crossing path at 68 mph; roof sheered off [14]. | Driver inattention; truck operator failure to yield; clear line of sight available to engaged driver [14]. | **Settled / Partially Adjudicated:** Emphasized persistent sensor perception limits regarding crossing freight trailers [15]. |
| ***Neima Benavides v. Tesla, Inc.*** (2024–2025) [19] | U.S. District Court, S.D. Florida | Tesla Autopilot (2019 Model S) | Design defect, failure to warn, defective driver monitoring; collision with parked vehicle causing passenger death [15]. | Driver sole proximate cause; Daubert challenges against plaintiff human-factors expert witnesses [19]. | **Pre-Trial Rulings:** Addressed admissibility of human factors testimony regarding complacency and punitive damages thresholds [19]. |

These civil proceedings show that defense verdicts in *Hsu* and *Lee* were supported by clear telemetric proof of driver error, such as long periods of hands-off driving, distraction, or intoxication [18]. In contrast, manufacturers have settled cases like *Huang* when discovery revealed internal engineering awareness of recurring perception errors or when court rulings admitted critical NTSB or NHTSA findings [5].

Plaintiffs succeed in surviving summary judgment by pairing human factors testimony with telematics logs to argue that a system's permissive operational envelope predictably invites the precise inattention that leads to the collision [5].

### Criminal Culpability in Semi-Autonomous Driving: People v. Kevin George Aziz Riad

The legal boundary between machine intervention and personal criminal culpability was tested in ***People v. Kevin George Aziz Riad*** (Los Angeles County Superior Court, 2019–2023) [42].

In December 2019, Riad was operating a Tesla Model S with Autopilot engaged on State Route 91 [20]. The vehicle exited the freeway onto Artesia Boulevard in Gardena, passed through a red traffic signal at 74 mph, and slammed into a Honda Civic, killing occupants Gilberto Alcazar Lopez and Maria Guadalupe Nieves-Lopez [20].

The Los Angeles County District Attorney charged Riad with two felony counts of vehicular manslaughter with gross negligence, marking the first felony prosecution in the United States of an operator using a semi-automated driving system [39].

Telemetric analysis revealed that Riad's hands were touching the steering wheel—satisfying the vehicle's passive torque sensor requirements—and that Autopilot issued no takeover warnings, yet crash logs recorded no manual braking during the six minutes preceding the collision [20].

Riad’s defense counsel argued that the driver relied on the vehicle's automated driver-assist system, which unexpectedly failed to slow down or navigate the exit ramp, negating the gross negligence required for a felony conviction [42].

The court rejected this argument, ruling that the operation of an SAE Level 2 driver assistance system does not relieve the human operator of the statutory duty to control the vehicle and obey traffic laws [42]. The driver remains the primary operator of the vehicle [20].

In June 2023, Riad pleaded no contest to two counts of vehicular manslaughter, receiving a sentence of two years of formal probation, 90 days of home confinement, and mandatory community service [43].

This outcome established an important criminal precedent: relying on Level 2 automation cannot be raised as an affirmative defense to negate personal criminal negligence [28]. The law continues to hold the human driver criminally responsible for moving violations and fatal collisions resulting from system operation [7].

## Comparative International Statutory Regimes

Recognizing the limits of conventional tort law in resolving shared-control accidents, several foreign jurisdictions have established statutory frameworks that allocate liability across automated systems, drivers, and insurers [46].

| Statutory Metric | Germany: StVG §§ 1a, 1b, 63a [47] | United Kingdom: AEVA 2018 / AVA 2024 [7] | European Union: Revised PLD / UN Reg 157 [10] |
| --- | --- | --- | --- |
| **Legal Classification of Human Operator** | Retains legal status of "Driver" (*Fahrzeugführer*) under § 1a(4) [47]. | Designated as "User-in-Charge" (UiC) during automated journeys under AVA 2024 [51]. | Fallback user; becomes primary driver following expiration of Takeover Request under UN Reg 157 [10]. |
| **Statutory Duty During Automation** | Permitted to turn attention from traffic; must remain alert enough to retake control immediately upon prompt (§ 1b) [47]. | Immune from criminal prosecution for moving violations while automated feature is engaged [51]. | Driver permitted to engage in non-driving tasks; must resume manual control within a 10-second transition window [10]. |
| **Third-Party Victim Recovery Mechanism** | Direct claim against keeper's mandatory liability insurer under strict liability (§ 7 StVG) [47]. | Direct claim against vehicle's motor insurer under Section 2 of AEVA 2018; no need to prove product defect [55]. | Direct recovery via revised Product Liability Directive; features rebuttable presumptions of defect and causation [50]. |
| **Manufacturer / Upstream Liability Locus** | Subrogation action by insurer against OEM under general Product Liability Act (*ProdHaftG*) [47]. | Statutory subrogation under Section 5 AEVA against Authorized Self-Driving Entity (ASDE) [46]. | Producer strictly liable for software defects, over-the-air update failures, and AI classification errors [50]. |
| **Mandatory Event Data Recording** | § 63a StVG: Logs time/location coordinates, control transfers, TORs, and technical faults (3-year retention) [47]. | AVA 2024 Data Code & DSSAD: Logs control transitions, transition demands, and manual overrides [7]. | UN Reg 157 DSSAD: Retains timestamps for activations, deactivations, transition demands, and system faults [10]. |
| **Statutory Compensation Limits** | Caps on strict keeper liability doubled for automated modes: €10M (injury/death), €2M (property) [49]. | Standard unlimited third-party personal injury motor liability insurance obligations apply [46]. | Member State strict product liability frameworks apply, subject to harmonized EU procedural presumptions [48]. |

### The German Model: StVG §§ 1a, 1b, and 63a Data Logging

The German Road Traffic Act (*Straßenverkehrsgesetz* - StVG) balances driver flexibility with ongoing responsibility [49]. Under **§ 1a StVG**, motor vehicles equipped with automated driving functions are permitted on public roadways, with paragraph 4 clarifying that the human who activates the system remains the legal driver (*Fahrzeugführer*) during automated operation [47].

Under **§ 1b StVG**, the law formalizes driver obligations during automation [47]. Paragraph 1 allows the driver to turn their visual attention away from the road to engage in secondary tasks, provided they remain capable of resuming manual control at any time [47].

Paragraph 2 requires the driver to immediately re-assume control under two distinct conditions: when the system issues a Takeover Request, or when the driver recognizes, or should recognize based on obvious external circumstances, that the system has exceeded its operational design domain [47].

To resolve factual disputes over who was controlling the vehicle at the time of an incident, **§ 63a StVG** requires an onboard event recorder that logs satellite time and location coordinates, system control transitions, takeover prompts, and technical disengagements [47].

Data must be retained for six months, or three years if the vehicle is involved in a collision, providing an evidentiary record to determine whether a crash resulted from an algorithmic defect or a driver's failure to respond to a prompt [47].

Civil liability is structured around strict keeper liability (*Halterhaftung*) under **§ 7 StVG**, under which the vehicle keeper is strictly liable for personal injury or property damage resulting from vehicle operation [47].

To account for automated vehicle risks, the legislature doubled the statutory liability caps under **§ 12 StVG** for automated driving phases to €10,000,000 for personal injury and €2,000,000 for property damage [49].

Injured third parties recover directly from the vehicle's mandatory motor insurer, which then retains subrogation rights against the manufacturer under product liability law if a software or hardware failure caused the incident [47].

### The British Paradigm: AEVA 2018 and the Automated Vehicles Act 2024

The United Kingdom has established a comprehensive legislative structure for automated driving through the **Automated and Electric Vehicles Act 2018 (AEVA)** and the **Automated Vehicles Act 2024** [7]. Under **Section 2 of AEVA 2018**, the UK introduced a single-insurer model: when an accident is caused by an automated vehicle driving itself on a road or other public place in Great Britain, the insurer is directly liable for the resulting damage [55].

Injured third parties and vehicle occupants do not have to initiate complex product liability lawsuits against software developers or global automotive original equipment manufacturers (OEMs) [1].

Instead, the victim files a claim directly against the vehicle's motor insurer [46]. Under **Section 5 of AEVA**, the insurer then steps into the victim's shoes through statutory subrogation to seek recovery from the responsible party—typically the vehicle manufacturer or automated system developer—under the Consumer Protection Act 1987 or standard negligence principles [1].

The **Automated Vehicles Act 2024** expanded this framework by defining distinct regulatory entities and legal protections [46]:

- The statutory "self-driving test" authorizes a vehicle feature as self-driving only if it can travel safely and legally without requiring human monitoring or intervention, excluding standard Level 2 assistance systems that require continuous oversight [7].
- Every authorized vehicle must be linked to an Authorized Self-Driving Entity (ASDE)—typically the vehicle manufacturer or software developer—which assumes legal and regulatory responsibility for the vehicle's driving behavior [7].
- When an authorized automated feature is active, the human occupant in the driver's seat becomes a "User-in-Charge" (UiC) and receives statutory immunity from criminal traffic offenses arising from dynamic driving maneuvers, such as speeding or running red signals [7]. Criminal culpability reattaches only if the UiC fails to respond safely to a formal Transition Demand, or commits non-driving infractions like driving under the influence or failing to maintain insurance coverage [7].
- The Act criminalizes misleading marketing, making it an offense to advertise or describe driver-assistance technologies using restricted terms that could lead consumers to believe a vehicle is self-driving when it has not been formally authorized as such [52].

### International Harmonization: UN Regulation No. 157 and the Revised EU Product Liability Directive

At the supranational level, the United Nations Economic Commission for Europe (UNECE) established the first international type-approval standard for automated vehicles through **UN Regulation No. 157**, governing Automated Lane Keeping Systems (ALKS) [10].

The regulation requires that an ALKS issue an escalating, multi-modal Transition Demand whenever it reaches the boundary of its operational design domain, detects a sensor failure, or encounters an operational condition it cannot handle [10].

The regulation mandates a minimum transition window of at least **10 seconds** for the human driver to resume manual control [10].

If the driver fails to respond within this window, the system must execute an automated **Minimum Risk Maneuver (MRM)** to bring the vehicle to a safe stop within its lane or onto the road shoulder while activating emergency flashers [10].

UN Regulation No. 157 also mandates the integration of an independent Data Storage System for Automated Driving (DSSAD) that records timestamps for every system activation, deactivation, transition demand, driver override, and technical fault, establishing a verified audit trail to confirm who had operational control during a crash [10].

Complementing these technical rules, the European Union updated its civil liability framework through the **Revised Product Liability Directive** [50].

To address the informational imbalance injured plaintiffs face when litigating against manufacturers of complex, black-box artificial intelligence systems, the revised directive introduced two evidentiary presumptions [50].

First, courts apply a rebuttable presumption of product defectiveness where a defendant manufacturer fails to comply with judicial evidence disclosure orders or where the plaintiff shows that the system violated applicable safety regulations or malfunctioned under ordinary use [50].

Second, the directive establishes a rebuttable presumption of causal connection where a plaintiff proves a product defect and shows that the defect was likely responsible for the resulting harm, addressing the complex task of proving causal chains in self-learning automated driving software [50].

## Strategic Recommendations for Regulatory and Tort Reform

To resolve the legal and technical tensions of shared human-machine vehicle control, policymakers and regulatory agencies should adopt a comprehensive framework centered on four core pillars:

### Pillar I: Mandatory Technical Enforceability Standards

Federal safety authorities, including NHTSA, should amend safety standards (such as the FMVSS framework) to prohibit passive, steering-wheel torque monitoring as an acceptable primary method of confirming driver engagement in SAE Level 2 vehicles [5]. All Level 2 systems should be required to incorporate direct, closed-loop driver monitoring systems (DMS) using infrared optical cameras capable of tracking eye-gaze direction, eyelid closure, and head orientation [5]. When the DMS detects visual distraction or inattention exceeding \(2.0\text{ seconds}\), the system must follow a standardized escalation protocol [5].

| Escalation Phase | Trigger Threshold | System Operational Response | Mechanical & HMI Execution |
| --- | --- | --- | --- |
| **Phase 1: Visual-Acoustic Alert** | Gaze diversion from roadway \(>2.0\text{ seconds}\) [5]. | System initiates prominent visual warnings on heads-up display and primary cluster paired with high-frequency chime [5]. | Lateral and longitudinal automated assistance remains engaged; system actively scans for driver eye re-engagement [5]. |
| **Phase 2: Haptic Intervention** | Driver distraction persists unresolved after \(3.0\text{ seconds}\) | System escalates warning through physical tactile channels to interrupt cognitive disengagement [6]. | Rapid brake pulse (jerk), directional steering wheel vibrations, and active seatbelt pre-tensioning [6]. |
| **Phase 3: Minimum Risk Maneuver (MRM)** | Inattention persists unresolved after \(5.0\text{ seconds}\) | System initiates automated fallback maneuver to bring vehicle to a controlled stop [6]. | Gradual deceleration within travel lane or onto shoulder, hazard warning light activation, and post-stop horn activation [10]. |
| **Phase 4: Post-Event Lockout** | Non-responsive driver or intentional defeat of DMS sensors | System prevents feature reactivation for the remainder of the current vehicle ignition cycle [5]. | Software locks out Level 2 assistance until vehicle is parked and restarted; logs driver monitoring failure [5]. |

Alongside mandatory optical monitoring, regulators should require manufacturers to implement strict Operational Design Domain (ODD) geofencing [5]. Level 2 lateral steering assistance should be electronically prevented from engaging on surface streets with unprotected cross-traffic, pedestrian crossings, or non-separated opposing traffic lanes [5]. Restricting system engagement to verified access-controlled freeways would prevent the operational mismatches that led to the fatalities examined in *Hsu*, *Riad*, and NHTSA EA22-002 [5].

### Pillar II: Evidentiary Standardization and Open Telematics

To eliminate the evidentiary imbalances that currently complicate civil litigation and regulatory crash investigations, regulatory authorities should establish comprehensive data-logging standards for vehicles equipped with ADAS and ADS platforms [5].

Federal regulations, such as 49 CFR Part 563 in the United States, should be expanded to mandate that event data recorders capture synchronized control metrics at a minimum frequency of \(10\text{ Hz}\) for sixty seconds prior to a collision [13].

These records must log lateral and longitudinal control authority, driver-facing monitoring metrics (including gaze vectors and eyelid tracking), manual driver inputs (steering torque, accelerator pressure, and braking force), automated perception classifications, and the precise timing of any system-issued Takeover Requests or disengagements [5].

Furthermore, regulators should require vehicle manufacturers to provide standardized, non-proprietary extraction tools that allow crash investigators, law enforcement personnel, and insurance adjusters to retrieve crash telemetry without relying on proprietary manufacturer software [15].

Requiring open-standard diagnostic readouts within forty-eight hours of an incident would prevent delays and ensure that liability determinations are based on objective technical logs rather than adversarial discovery disputes [15].

### Pillar III: Evidentiary Presumptions and Anti-Autonowashing Protections

Civil tort doctrine should adapt to the technical complexity of automated driving by establishing balanced evidentiary presumptions in products liability actions [50].

Following the model of the revised EU Product Liability Directive, state and federal courts should apply a rebuttable presumption of product defectiveness whenever an automotive OEM fails to maintain or produce required DSSAD crash logs, or when an ADAS-equipped vehicle collides with a stationary obstacle within its documented design envelope without issuing an automated brake command or timely Takeover Request [5].

Once this presumption attaches, the burden shifts to the manufacturer to prove that the crash was caused entirely by the driver's gross negligence or intentional intervention [19].

To prevent consumer confusion over automated driving capabilities, federal and state legislatures should enact statutory bans against deceptive marketing in driver assistance technologies, modeled on the UK Automated Vehicles Act 2024 [52].

These statutes should make it an unlawful trade practice to market, label, or advertise an SAE Level 2 assistance feature using terminology such as "Autopilot," "Full Self-Driving," "Automated Driving," or "Pilot Assist," unless the system has received formal type-approval for operation without continuous human supervision [21].

Violations should incur administrative civil penalties and create a statutory presumption of consumer reliance in civil failure-to-warn and fraud claims [18].

### Pillar IV: Insurance Architecture and Channeled Liability

For vehicles equipped with SAE Level 3 conditional driving automation, jurisdictions should transition from conventional, fault-based tort litigation to a single-insurer direct compensation scheme modeled on the UK Automated and Electric Vehicles Act 2018 [46].

Under this framework, injured third parties and vehicle occupants file direct claims against the vehicle's mandatory motor insurance policy, obtaining prompt compensation for personal injury and property damage without being forced to prove complex algorithmic defects or litigate against automotive manufacturers [46].

The primary insurer is held strictly liable in the first instance, ensuring that accident victims receive medical coverage and financial recovery without procedural delay [46].

Following initial victim compensation, the insurer is granted statutory subrogation rights to recover damages from the vehicle manufacturer or automated software developer through an expedited inter-industry arbitration process [1].

This arbitration framework would evaluate verified DSSAD telemetry:

- If the vehicle was operating in an active automated mode within its validated ODD and failed to execute a safe stop or provide a 10-second Transition Demand, financial liability remains with the vehicle manufacturer [10].
- If the telemetry confirms that the system issued a timely Transition Demand and the human operator failed to resume manual control, or if the operator intentionally bypassed system alerts, liability is allocated to the driver [46].

This structure provides injured victims with immediate access to compensation while maintaining an efficient subrogation channel that holds automotive manufacturers accountable for the safety and performance of automated driving software [46].

By aligning technical standards, evidentiary transparency, and statutory compensation schemes, regulatory frameworks can allocate liability fairly across the human-machine driving interface [2].

## References

[1] Driverless cars: when nobody is driving, who pays for the crash? — https://iclg.com/news/driverless-cars-when-nobody-is-driving-who-pays-for-the-crash/
[2] Opportunities and Challenges of Operating Semi-Autonomous — https://www.researchgate.net/publication/401470226_Opportunities_and_Challenges_of_Operating_Semi-Autonomous_Vehicles_A_Layered_Vulnerability_Perspective
[3] Explainable Artificial Intelligence for Autonomous Driving - arXiv — https://arxiv.org/html/2112.11561v4
[4] ODI RESUME - nhtsa — https://static.nhtsa.gov/odi/inv/2022/INCLA-EA22002-14498.pdf
[5] Additional Information Regarding EA22002 Investigation - nhtsa — https://static.nhtsa.gov/odi/inv/2022/INCR-EA22002-14496.pdf
[6] Tort Liability, Privacy, and Regulatory Considerations for Level 3 — https://repository.law.umich.edu/cgi/viewcontent.cgi?article=1059&context=mtlr
[7] Automated Vehicles Act 2024, Explanatory Notes - Legislation.gov.uk — https://www.legislation.gov.uk/ukpga/2024/10/pdfs/ukpgaen_20240010_en.pdf
[8] NHTSA concludes Tesla Autopilot investigation after linking the — https://www.engadget.com/nhtsa-concludes-tesla-autopilot-investigation-after-linking-the-system-to-14-deaths-161941746.html
[9] Before You Let Go of the Wheel: Do You Understand the Levels of — https://www.aminext.blog/en/post/sae-autonomous-driving-levels-explained-1
[10] Automated lane keeping systems - Wikipedia — https://en.wikipedia.org/wiki/Automated_lane_keeping_systems
[11] From Assistance to Autonomy: Nonlinear Human Factors and ... - MDPI — https://www.mdpi.com/2071-1050/18/12/6033
[12] What determines the take-over time? An integrated model approach — https://www.researchgate.net/publication/273833386_What_determines_the_take-over_time_An_integrated_model_approach_of_driver_take-over_after_automated_driving
[13] Standing General Order on Crash Reporting - NHTSA — https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting
[14] Banner Family Lawsuit Against Tesla | PDF - Scribd — https://www.scribd.com/document/595544445/Banner-family-lawsuit-against-Tesla
[15] Tesla withheld data, lied, misdirected police to avoid blame in — https://news.ycombinator.com/item?id=44787780
[16] Who Is Liable in an AV Crash? A Guide for Corporate Risk Managers — https://www.journalives.com/who-is-liable-when-a-self-driving-corporate-car-crashes-during-business-hours/
[17] Explainable Artificial Intelligence for Autonomous Driving - arXiv — https://arxiv.org/html/2112.11561v5
[18] Top Product Liability Cases Of 2023: Midyear Review - Mayer Brown — https://www.mayerbrown.com/-/media/files/news/2023/07/top-product-liability-cases-of-2023-midyear-review.pdf%3Frev=-1
[19] Benavides v. Tesla, Inc | 21-21940 | S.D. Fla. | Judgment - CaseMine — https://www.casemine.com/judgement/us/68604cbb69d6968192f03465
[20] Driver to stand trial in Tesla autopilot crash which killed two in — https://www.cbsnews.com/losangeles/news/driver-to-stand-trial-in-tesla-autopilot-crash-which-killed-two-in-gardena/
[21] Tesla's Autopilot and FSD have been linked to hundreds of crashes — https://gigazine.net/gsc_news/en/20240428-tesla-autopilot-full-self-driving-crashes-deaths/
[22] Identify defective products liability... - Varsity Tutors — https://www.varsitytutors.com/practice/subjects/bar-exam-uniform/lessons/products-liability
[23] Litigating Partial Autonomy — https://scholarlycommons.law.case.edu/cgi/viewcontent.cgi?article=3188&context=faculty_publications
[24] Product Liability: Warnings, Instructions, and Recalls: Illinois — https://johnsonandbell.com/wp-content/uploads/2019/04/Duty-to-Warn-Illinois.pdf
[25] Categorical Liability for Manifestly Unreasonable Designs — https://scholarship.law.cornell.edu/cgi/viewcontent.cgi?article=2606&context=clr
[26] Litigation Trends on the 10th Anniversary of the Third Restatement — https://scholarship.kentlaw.iit.edu/cgi/viewcontent.cgi?article=1718&context=fac_schol
[27] Ch 21 -… Flashcards, Test Prep & Study Guide | Cram — https://www.cram.com/flashcards/ch-21-warranties-and-product-liability-2628176
[28] Criminal Charges & Civil Lawsuits in California Tesla Autopilot Crash — https://www.enjuris.com/blog/ca/tesla-autopilot-crash/
[29] NHTSA closes investigation into Autopilot driver controls, opens — https://www.reddit.com/r/teslainvestorsclub/comments/1cdrtqj/nhtsa_closes_investigation_into_autopilot_driver/
[30] Tesla Model 3 NHTSA Investigations - Verify the Vehicle — https://verifythevehicle.com/investigations/tesla/model-3
[31] NHTSA Amends Standing General Order on Reporting ADS — https://www.ballardspahr.com/insights/alerts-and-articles/2023/04/nhtsa-amends-standing-general-order-on-reporting-ads--and-adas-involved-crashes
[32] Incident Reporting for Automated Driving Systems (ADS) and Level — https://www.federalregister.gov/documents/2026/03/04/2026-04240/agency-information-collection-activities-notice-and-request-for-comment-incident-reporting-for
[33] Third Amendment | Standing General Order 2021-01 - NHTSA — https://www.nhtsa.gov/sites/nhtsa.gov/files/2025-04/third-amended-SGO-2021-01_2025.pdf
[34] Risk Quarterly 5 Sign Up - Feb 2026 - Clyde & Co — https://my.clydeco.com/experience-rq-issue5-preview/p/4
[35] Justine Hsu v. Tesla, Inc. :: Superior Court of California ... - PlainSite — https://www.plainsite.org/dockets/49wlklo0l/superior-court-of-california-county-of-los-angeles/justine-hsu-v-tesla-inc/
[36] Tesla Full Self-Driving issues with motorcycle riders - Facebook — https://www.facebook.com/groups/CyberTruck/posts/27481834378152079/
[37] Case 3:22-cv-05240-RFL Document 61 Filed 10/30/23 Page 1 of 124 — https://www.pacermonitor.com/view/QEZLOBY/Matsko_v_Tesla_Inc_et_al__candce-22-05240__0061.0.pdf
[38] Walter Huang's Instagram, Twitter & Facebook on IDCrawl — https://www.idcrawl.com/walter-huang
[39] First felony charges filed involving fatal Tesla autopilot crash — https://www.denvergazette.com/2022/01/19/first-felony-charges-filed-involving-fatal-tesla-autopilot-crash/
[40] September 27, 2024 - Reginfo.gov — https://www.reginfo.gov/public/do/DownloadDocument?objectID=151609400
[41] NEIMA BENAVIDES, Personal Representative of the ... - PlainSite — https://www.plainsite.org/dockets/4jjpwqq1c/florida-southern-district-court/neima-benavides-personal-representative-of-the-estate-of-naibel-benavides-leon-deceased-v-tes/
[42] Judge orders trial in Tesla autopilot manslaughter case — https://www.courthousenews.com/judge-orders-trial-in-tesla-autopilot-manslaughter-case/
[43] Tesla Driver in Fatal Model S Crash in CA Gets Probation — https://www.autobodynews.com/news/tesla-driver-in-fatal-model-s-crash-in-ca-gets-probation
[44] US driver in Tesla 'Autopilot' crash which killed two motorists avoids — https://www.drive.com.au/news/tesla-autopilot-fatal-crash-conviction/
[45] Landmark trial involving Tesla autopilot weighs if 'man or machine — https://www.theguardian.com/technology/2022/nov/14/tesla-autopilot-landmark-case-man-v-machine
[46] Autonomous vehicle insurance | Apex Insurance Brokers Wiki — https://apexinsurancebrokers.co.uk/wiki/autonomous-vehicle-insurance/
[47] German Bundestag adopts law on automatic driving - Noerr — https://www.noerr.com/en/insights/bundestag-verabschiedet-gesetz-zum-automatisierten-fahren
[48] (PDF) Automated Vehicles and Third-Party Liability: A European — https://www.researchgate.net/publication/338584763_Automated_Vehicles_and_Third-Party_Liability_A_European_Perspective
[49] 1 English Translation of the German Road Traffic Act Amendment — https://www.researchgate.net/profile/Krzysztof-Czarnecki-2/publication/320813344_English_Translation_of_the_German_Road_Traffic_Act_Amendment_Regulating_the_Use_of_Motor_Vehicles_with_Highly_or_Fully_Automated_Driving_Function_from_July_17_2017/links/59fbbe680f7e9b9968bb5a0f/English-Translation-of-the-German-Road-Traffic-Act-Amendment-Regulating-the-Use-of-Motor-Vehicles-with-Highly-or-Fully-Automated-Driving-Function-from-July-17-2017.pdf
[50] A Comparative Critique of AI 'Legal Personhood' and Liability — https://grnjournal.us/index.php/AJPDIS/article/download/9038/8775/16665
[51] Automated Vehicles Act 2024: A deeper dive into its key implications f — https://cms.law/en/gbr/legal-updates/automated-vehicles-act-2024-a-deeper-dive-into-its-key-implications-for-the-automotive-sector
[52] Automated Vehicles Act 2024: UK self-driving vehicle law — https://netzerocompare.com/policies/uk-automated-vehicles-act
[53] L3Pilot Code-of-Practice for the Development of Automated Driving — https://www.researchgate.net/publication/355377506_L3Pilot_Code-of-Practice_for_the_Development_of_Automated_Driving_Functions
[54] New Level 3 Autonomous Driving Regulations for European — https://www.cbwonline.com/eu-level-3-autonomous-driving-regulations-2026.html
[55] CONTRIBUTION CLAIMS AGAINST THIRD PARTIES UNDER THE — https://aevlaw.com/blog/contribution-claims-against-third-parties-under-the-automated-and-electric-vehicles-act-2018/
[56] Automated and Electric Vehicles Act 2018 - Stewarts Law — https://www.stewartslaw.com/news/unanswered-questions-following-automated-electric-vehicles-act-2018/
[57] Product Liability & Safety 2026 - Austria | Global Practice Guides — https://practiceguides.chambers.com/practice-guides/product-liability-safety-2026/austria
[58] Automated and Electric Vehicles Act 2018 - Legislation.gov.uk — https://www.legislation.gov.uk/ukpga/2018/18/section/2
[59] Self‑Driving Cars & E‑Scooters UK 2026: Laws, Liability & Safety — https://saracenssolicitors.co.uk/future-of-the-road-self-driving-cars-e-scooter-laws-uk-2026/
[60] The Automated Vehicles Act 2024 becomes law in the UK - The Lens — https://thelens.slaughterandmay.com/post/102j8ih/the-automated-vehicles-act-2024-becomes-law-in-the-uk
[61] Automated Vehicles Act 2024: revolutionising the future of — https://www.ashfords.co.uk/insights/articles/automated-vehicles-act-2024-revolutionising-the-future-of-transportation
[62] Legal, Regulatory and Ethical Framework – M18 D7.2 - European — https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5243acfcb&appId=PPGMS
[63] ARTIFICIAL INTELLIGENCE AND LEGAL LIABILITY - Record Of Law — https://recordoflaw.in/artificial-intelligence-and-legal-liability-who-is-responsible-for-ai-decisions/
[64] QUARTERLY UPDATE - HF — https://www.h-f.co.uk/wp-content/uploads/2022/12/Product-Liability-bitesize-Dec-22.pdf
[65] Grounding the case for a European approach to the regulation ... - IRIS — https://www.iris.sssup.it/retrieve/dd9e0b32-5172-709e-e053-3705fe0a83fd/Bertolini-Riccaboni2020_Article_GroundingTheCaseForAEuropeanAp.pdf


Please begin the extraction now. Output only the JSON list directly, without any chitchat or explanations.