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:
# Liability Allocation in ADAS-Equipped Vehicles with Shared Human–Machine Control

## Executive Summary

Advanced driver-assistance systems (ADAS) increasingly perform continuous longitudinal and lateral control while still legally requiring a human driver to supervise and intervene, creating a hybrid “collaborative driving” context. Existing tort and product liability doctrines mostly treat Level 2 ADAS vehicles as conventional vehicles whose drivers bear primary responsibility, but courts and regulators are beginning to recognize scenarios in which manufacturers, software developers, and even data controllers share liability when ADAS behavior contributes to accidents. Comparative negligence, strict product liability, and consumer protection law together govern how fault is allocated between drivers and ADAS providers.[1][2][3][4][5]

This report synthesizes technical characteristics of ADAS, current liability frameworks across jurisdictions, and emerging case law to map responsibility boundaries in shared-control crashes. It argues that traditional "driver is always in charge" narratives are increasingly inaccurate for modern supervised autonomy and that liability allocation should explicitly reflect human–machine collaboration, foreseeable automation-induced complacency, and the duty of manufacturers to design, warn, and update systems responsibly. The report concludes with proposed regulatory guidelines: (1) explicit statutory allocation rules keyed to automation mode and transition periods, (2) mandatory data retention and disclosure for accident reconstruction, (3) harmonized standards on driver monitoring and takeover requests, and (4) doctrines recognizing overstatement of autonomy as a form of misrepresentation or unfair practice.[2][1]

## Technical Foundations of ADAS and Shared Control

### ADAS Functions and Levels of Automation

ADAS encompasses a spectrum of technologies ranging from basic warnings (e.g., forward collision warning) to continuous control features such as adaptive cruise control, lane keeping assistance, automated lane keeping, and driver control assistance systems that combine longitudinal and lateral control. Under the SAE J3016 taxonomy, most systems currently deployed in consumer vehicles are Level 1 or Level 2—providing assistance with either steering or speed, or both, while requiring the human driver to remain responsible and able to take over at any time.[5][2]

Regulatory frameworks, especially in Europe under UNECE regulations, distinguish between Level 2 driver control assistance systems (DCAS) and higher-level automated lane keeping systems (ALKS). UN R171 addresses DCAS, where the driver must stay engaged with the system at all times, while UN R157 governs ALKS, which can manage both steering and speed on specific roads but still assumes the driver can be asked to take over. These standards embed technical requirements such as minimum sensing ranges, lane coverage, and minimum-risk maneuvers in case of system faults or driver non-intervention, implicitly assuming shared responsibility between human and machine.[5]

### Shared Human–Machine Driving Tasks

In partial autonomy, ADAS often performs continuous control of acceleration, braking, and steering within a defined operational design domain (ODD), while the human is expected to monitor and intervene when the system encounters limitations or exits its ODD. Scholars describe this as a "collaborative driving" endeavor where the human and computer share dynamic driving tasks over time. This shared control complicates traditional negligence analysis that assumed a single human driver was responsible for all driving decisions.[6][2]

When a computer driver is engaged, some frameworks treat it as having operational responsibility for the dynamic driving task, with the manufacturer bearing liability for accidents proximately caused by the system’s negligent operation or design defects. Proposed statutory architectures allocate manufacturer liability during automated operation, with liability transitioning back to the human driver after a defined safe-harbor interval following a takeover request or driver-monitoring alert. These technical and temporal boundaries are central to allocating fault when ADAS-equipped vehicles crash.[6]

## Existing Legal Frameworks for ADAS Liability

### Tort Negligence and Comparative Fault

Traditional motor-vehicle accident liability rests on negligence: did the driver act as a reasonably prudent person under the circumstances, and was that conduct a proximate cause of the harm. Comparative negligence regimes allow fault to be allocated among multiple negligent actors, including drivers, other road users, and, increasingly, system providers whose design or warnings may have contributed to risk. In ADAS crashes, defense counsel often argue that inattentive drivers remain the primary proximate cause, while plaintiffs contend that system design foreseeably induces complacency or overtrust.[4][7][1][2]

Driver-focused negligence remains dominant in many jurisdictions. For example, practitioners in Florida describe that, despite driver-assistance features, the law usually expects a human driver to stay in control, and fault is primarily evaluated based on driver reasonableness under state negligence rules, subject to modified comparative fault that can divide liability among multiple parties. California analysis of ADAS malfunctions similarly emphasizes the driver’s duty to remain attentive, but acknowledges that defective sensors, software issues, or inadequate warnings may lead to shared responsibility under comparative fault.[7][4]

### Product Liability and Strict Liability for Defects

Product liability doctrines provide an alternative or complementary pathway: if a defective ADAS system, sensor, or software update contributes to a crash, manufacturers or component suppliers may be strictly liable for resulting harm. Under strict liability, plaintiffs typically must show that a defect made the product unreasonably dangerous, that the defect existed when sold, that the manufacturer created or sold the product, that the defect directly caused the injury, and that the product was used in a reasonably foreseeable manner without overriding safety features.[3][1]

Legal scholarship suggests that, while conventional ADAS collisions generally fit within traditional negligence analysis, true automated vehicles (AVs) likely make manufacturers the primary liable party because tort liability tracks autonomous agency—the entity exercising autonomous decision-making. Nonetheless, for ADAS-equipped vehicles, manufacturers’ exposure still arises when foreseeably dangerous system behaviors, programming limitations, sensor inaccuracies, or misleading marketing contribute to crashes. Product defect, failure-to-warn, and misrepresentation claims are particularly salient when manufacturers overstate autonomous capabilities or downplay limitations.[8][1][2]

### Consumer Protection and Misrepresentation of Autonomy

Consumer protection statutes and unfair or deceptive trade practice laws provide additional leverage where manufacturers overstate the automation or intelligence level of vehicles or fail to adequately disclose limitations. Chinese judicial guidance explicitly states that if producers or sellers engage in false or misleading publicity regarding a vehicle’s automation level, intelligence, performance, or usage, courts should support consumers’ claims for civil liability under the Civil Code and consumer rights statutes.[9][10]

Scholars in the United States similarly recommend that customers pursue fraud and warranty claims when manufacturers overstate autonomous capabilities, arguing that economic-damages litigation can encourage manufacturers to internalize the cost of defects before serious injuries occur. Overstated marketing can also affect negligence analysis by undermining the assumption that drivers knowingly accepted supervision duties, thereby shifting some blame toward manufacturers.[2]

## Emerging Case Law in Shared Human–Machine Crashes

### Criminal Cases: Human Drivers Still Primary Actors

Criminal prosecutions in several jurisdictions have reaffirmed that human drivers remain responsible in accidents involving ADAS features, particularly at Level 2. In California, a judge sentenced a driver to probation after he pled no contest to vehicular manslaughter with gross negligence for causing a fatal accident while using Tesla’s Autopilot, which ran a red light. In Arizona, the safety driver in an Uber self-driving test vehicle received probation for a pedestrian fatality where the system failed to recognize a jaywalker, again treating the human as the criminally responsible party.[3]

Chinese guidance on intelligent driving further clarifies criminal liability where drivers deliberately evade ADAS monitoring systems—for example, using accessories that simulate hands on the wheel to bypass hands-off alerts. If such actions, combined with activation of assisted driving, cause a traffic accident and meet the threshold for a crime, criminal liability will be pursued. Courts emphasize that onboard assisted driving systems cannot replace the driver as the primary entity responsible for driving; the driver remains the person actually executing the driving task after activating assistance.[10]

### Civil Cases: Shared Responsibility and Manufacturer Exposure

Civil litigation in ADAS crashes shows a more nuanced allocation. A landmark Florida case, Benavides v. Tesla, resulted in a jury awarding more than $240 million, including substantial punitive damages, after finding Tesla partially responsible for a fatal 2019 accident involving Autopilot. This was one of the first U.S. verdicts to hold Tesla liable in a wrongful-death action tied directly to Autopilot’s operation, indicating that juries may conclude that system behavior and warnings played a significant causal role alongside driver conduct.[11]

Broader analysis of civil liability standards notes that two competing theories—traditional negligence (driver-focused) and strict product liability (manufacturer-focused)—are emerging in ADAS accidents. Courts readily apply conventional negligence where human behavior clearly causes accidents, but product liability becomes more salient as self-driving functionality expands, especially during transition periods where control shifts from technology to human occupants. Scholars propose that humans may remain immune from liability while the vehicle is driving autonomously, with liability kicking back in after a properly notified transition period ends, assuming the vehicle met its duty to alert occupants and avoided safety-feature overrides.[3]

In China, both judicial guidance and case law establish that drivers remain liable in Level 2 semi-autonomous systems, framing ADAS as supportive tools that do not replace driver responsibility. However, the Supreme People's Court opinion allows injured parties to seek compensation from both drivers and manufacturers when accidents involve a combination of vehicle defects and driver error, with liability apportioned based on contributions and degree of fault. This codifies shared responsibility in scenarios where ADAS malfunction interacts with driver negligence.[12][9][10]

### Evidentiary Innovations and Data Access

Modern ADAS-equipped vehicles generate extensive logs, event data recorder (EDR) entries, and software update histories that are increasingly central to accident reconstruction and liability allocation. Chinese judicial guidance explicitly authorizes courts to require data controllers—vehicle producers, sellers, or operators—to provide authentic and complete data necessary for establishing accident facts, including records of autonomous driving and ADAS events. Similarly, practitioner guidance in U.S. jurisdictions emphasizes evidence such as black-box data, system logs, dashboard warnings, software update history, recall notices, and calibration records to determine whether system defects, mis-calibration, or human inattentiveness were responsible.[10][4][7]

These developments support more granular allocation of responsibility—distinguishing between human and machine behavior in the seconds leading up to a crash, identifying whether takeover requests or alerts were issued and ignored, and determining whether known system limitations were foreseeable and properly disclosed.

## Systematic Boundaries of Responsibility

### Baseline Rule: Driver Responsibility in Supervised ADAS

Across jurisdictions, a baseline principle holds that Level 2 ADAS systems are driver-assistance tools, not substitutes for human drivers, meaning drivers remain legally responsible for safe vehicle operation. Regulatory frameworks such as UNECE’s DCAS and ALKS rules state that the driver must be ready to take over at any time and remains responsible, even when systems perform sustained longitudinal and lateral support. Practice-oriented guidance in California and Florida likewise underscores that drivers are usually expected to stay in control, and inattentiveness will typically factor into negligence analysis.[12][4][7][5]

Courts and regulators emphasize that activating assisted driving does not relieve drivers of their duty to monitor the road and system behavior. Chinese rulings and guidance describe drivers as the actual executors of the driving task after activating assistance and treat evasion of driver-monitoring mechanisms as aggravating misconduct. Criminal cases in the United States similarly hold drivers accountable for grossly negligent use of ADAS when it leads to fatalities.[10][12][3]

### Manufacturer and System Responsibility: Defects, Design, and Warnings

Manufacturers, software developers, and component suppliers bear responsibility where ADAS defects or design choices contribute to accidents. Product liability attaches when defective sensors, software bugs, failed over-the-air updates, or improper calibration make systems unreasonably dangerous and directly cause harm under reasonably foreseeable use. Design decisions that create foreseeable automation complacency, such as unclear takeover requests, inadequate driver-monitoring, or misleading HMI cues, may also be evaluated under negligence or strict liability.[1][4][7]

Legal scholarship argues that manufacturers share responsibility in modern supervised autonomy because collaborative driving arrangements mean drivers cannot always react in time when systems act unexpectedly, particularly if they reasonably trusted marketing claims or system behavior. When trust is misplaced and drivers are unable to re-take control promptly, automakers may face primary liability with reductions for comparative fault. Consumer protection doctrines further impose liability for false or misleading claims about automation or intelligence levels, and guidance such as that from China’s Supreme People's Court explicitly supports civil claims where such publicity harms consumers’ rights.[9][2][10]

### Shared Fault: Interaction of Human Error and System Behavior

Many ADAS accidents involve both driver negligence (e.g., inattention, misuse, override of safety features) and system limitations or defects (e.g., sensor blind spots, software faults, mis-calibration). Comparative negligence and multi-cause tort theories allow courts to apportion liability between drivers and manufacturers based on relative contributions.[7][1][9]

Chinese guidance explicitly recognizes scenarios where combined "defect + fault" cause identical damage, instructing courts to support claims that both drivers and producers or sellers bear compensation liability according to relevant Civil Code provisions. In the U.S., practitioners highlight how defective sensors, dangerous system design, or recalled driver-assistance features can share responsibility with driver inattentiveness under comparative fault rules. Academic proposals, like those in Iowa Law Review and Jurimetrics, recommend statutory architectures in which manufacturer liability applies when the computer driver is operating negligently in autonomous or supervisory modes, with liability gradually transitioning back to humans after effective takeover requests and reasonable intervals.[4][9][2][6][7][10]

### Temporal Boundaries: Takeover Requests and Safe-Harbor Intervals

One of the most challenging aspects of liability allocation is the transition from automated to human control. Jurimetrics scholarship proposes explicit temporal rules: manufacturer liability during supervisory mode commencing when the computer driver engages and potentially ceasing ten seconds after a driver-monitoring alert or takeover request, with courts determining reasonable intervals based on context. A short safe-harbor interval is suggested to align with European regulations and provide political consensus, with recommendations that supervisors consider longer intervals (e.g., 30–90 seconds) in complex scenarios.[6]

Other analyses similarly suggest that liability should be keyed to whether the vehicle properly notified occupants of failures or ODD exits and whether drivers had a fair opportunity to re-take control. If a vehicle fails to issue clear alerts or does so too late for reasonably attentive drivers to respond, responsibility may remain with manufacturers even after disengagement. Conversely, if drivers ignore clear and timely takeover requests, liability may shift back toward them.[3]

### Mode Distinctions: Conventional, Supervised Autonomy, and Full Automation

Legal frameworks increasingly differentiate between three modes:

- Conventional mode, where human drivers are fully responsible, and any automation is limited to non-continuous assist.
- Supervised autonomy (Level 2 and some Level 3 arrangements), where computer drivers perform dynamic tasks but humans must supervise and be ready to take over, leading to shared or shifting liability depending on system engagement and alerts.[2][5][6]
- Full automation (higher-level AVs), where manufacturers are generally expected to bear primary liability for the driving behavior of their vehicles, given that autonomous agency rests with the system.[8]

For ADAS-equipped vehicles, most accidents currently fall in supervised autonomy or conventional modes. Scholars like Geistfeld and commentators on UK’s Automated and Electric Vehicles Act note that, for truly automated vehicles driving themselves, insurers or manufacturers may be statutorily liable for death, personal injury, and property damage caused when the vehicle is driving itself. ADAS cases, however, must navigate more complex shared-responsibility boundaries.[13][8]

## Proposed Regulatory and Doctrinal Guidelines

### 1. Explicit Statutory Liability Allocation Rules

Regulators should codify liability allocation tied to automation modes and transition periods rather than relying exclusively on ad hoc negligence analysis. Building on Jurimetrics’ proposed architecture, statutes could provide:

- Manufacturer responsibility when the computer driver is engaged in supervisory or autonomous modes, covering negligence in perception, planning, control, driver monitoring, and takeover management.[6]
- A defined safe-harbor interval after effective alerts or takeover requests (e.g., 10 seconds minimum, potentially extendable to 30–90 seconds in complex conditions) during which liability is shared or unclear, allowing courts to assess context.[6]
- Clear rules that, once a reasonable transition period elapses and the human fails to respond to proper alerts, negligence presumptively shifts toward the human driver, subject to rebuttal if alerts are shown to be inadequate.[3][6]

Such statutes would reduce uncertainty in the "awkward middle" where humans and computers share driving responsibilities and improve ex ante risk allocation for manufacturers and drivers.

### 2. Mandatory Data Retention and Access for Accident Reconstruction

As intelligent vehicles generate extensive logs, regulators should mandate standardized data retention and access obligations. Judicial guidance in China already empowers courts to require data controllers to provide authentic and complete data on autonomous driving and ADAS events to ascertain accident causes. Similar rules could require:[10]

- Minimum retention periods for EDR data, ADAS logs, sensor outputs, and software update histories.
- Secure, privacy-preserving mechanisms for courts and investigators to access relevant data.
- Penalties or adverse evidentiary inferences for manufacturers or operators who fail to preserve or disclose data.

These measures would support accurate fault allocation, enable identification of systemic defects, and deter spoliation of evidence.[7][10]

### 3. Harmonized Standards on Driver Monitoring and Human–Machine Interface

Technical regulations like UNECE R157 and R171 should be complemented with detailed standards for driver-monitoring systems, takeover request design, and HMI cues that directly influence liability assessments. Regulators could require:[5][6]

- Robust driver-monitoring (e.g., camera-based attention detection) with escalating alerts when inattentiveness is detected.
- Clear, unambiguous takeover requests with standardized visual, auditory, and haptic signals.
- Minimum-risk maneuvers when drivers fail to respond within defined intervals.

By specifying what constitutes a "proper" alert and reasonable takeover opportunity, these standards would clarify when manufacturers have discharged their duties and when remaining risk lies with drivers.

### 4. Doctrines Recognizing Automation-Induced Complacency

Courts should explicitly consider automation-induced complacency and overtrust as foreseeable phenomena that manufacturers must account for. Scholarship on partial autonomy argues that modern supervised systems require collaborative driving, and drivers should not bear full liability when system design reasonably engenders misplaced trust.[1][2]

Regulatory guidance could instruct courts to:

- Evaluate whether system interfaces, marketing, and documentation reasonably mitigated overtrust.
- Treat failure to address known complacency risks as evidence of negligent design or inadequate warnings.
- Allow comparative fault reductions for drivers who reasonably relied on system behavior within its stated ODD, particularly when alerts were ambiguous or late.

This approach aligns liability with realistic human behavior in complex socio-technical systems and incentivizes safer interface design.[1][2]

### 5. Stronger Consumer Protection Against Misleading Autonomy Claims

Building on Chinese guidance and U.S. scholarship, regulators should treat overstated autonomy claims as deceptive practices subject to civil penalties, restitution, and enhanced liability.[9][2][10]

Guidelines might include:

- Banning terms like "self-driving" or "autopilot" for Level 2 systems absent prominent disclaimers that continuous human supervision is required.
- Requiring clear disclosures about automation levels, ODD limitations, and necessary driver engagement.
- Allowing consumers to pursue fraud, warranty, and unfair-practice claims for economic damages stemming from misrepresentations, even before physical injuries occur.[2]

These measures would reduce the gap between actual system capabilities and user expectations, thereby mitigating shared-control confusion and lowering accident risk.

### 6. Integration with Insurance and No-Fault Schemes

Jurisdictions that use compulsory auto insurance or no-fault schemes can integrate ADAS liability rules by, for example, placing first-line responsibility on insurers while reserving rights of subrogation against manufacturers and software providers when system defects contribute to losses. The UK’s Automated and Electric Vehicles Act already makes insurers liable for harm caused by automated vehicles when driving themselves while preserving recourse against manufacturers.[14][13]

Extending similar frameworks to supervised ADAS cases could ensure prompt compensation for victims while allowing sophisticated fault allocation and cost internalization among stakeholders. Insurers would have incentives to collect detailed data, identify patterns of defects or misuse, and press manufacturers for safer designs.[13][14]

## Conclusion

Liability allocation in accidents involving ADAS-equipped vehicles in shared human–machine driving contexts sits at the intersection of technical system design, evolving tort and product liability doctrines, and emerging regulatory guidance. Current law generally treats Level 2 ADAS as driver-assistance tools, preserving primary driver responsibility, but product liability, comparative fault, and consumer protection frameworks increasingly recognize manufacturer and system responsibility where defects, design limitations, or misleading marketing contribute to crashes.[4][9][1][2]

To address the "awkward middle" between conventional driving and full automation, regulators and courts should adopt explicit mode-based liability rules, mandate robust data access for accident reconstruction, harmonize driver-monitoring and takeover standards, recognize automation-induced complacency as a foreseeable design consideration, and strengthen consumer protection against autonomy overstatement. These measures would better reflect collaborative driving realities, promote safer ADAS deployment, and provide clearer ex ante expectations for drivers, manufacturers, and insurers as intelligent transportation systems continue to evolve.[5][10][6]

## References

[1] https://www.thefederation.org/docs/Events/2026/Annual/CLE/9-Asleep.pdf
[2] https://ilr.law.uiowa.edu/volume-109-issue-4/litigating-partial-autonomy
[3] https://bpb-us-e1.wpmucdn.com/sites.suffolk.edu/dist/3/1172/files/2025/06/04_SLR_58-1_Marini.pdf
[4] https://www.penneylawyers.com/car-accidents/adas-malfunctions-and-car-accidents-when-technology-contributes-to-injury/
[5] https://www.fiaregion1.com/wp-content/uploads/2026/01/Final_Report_ADAS_DCAS_FIA_2025.pdf
[6] https://www.americanbar.org/content/dam/aba/publications/Jurimetrics/fall2023/the-awkward-middle-for-automated-vehicles-liability-attribution-rules-when-humans-and-computers-share-driving-responsibilities.pdf
[7] https://www.injurylawyers.com/blog/when-advanced-driver-assistance-systems-fail-who-is-liable-in-car-accident/
[8] https://scholar.law.colorado.edu/cgi/viewcontent.cgi?article=1025&context=ctlj
[9] https://global.chinadaily.com.cn/a/202609/14/WS6aa75559e4b06d4aa055de04.html
[10] https://news.futunn.com/en/post/78960308/the-supreme-people-s-court-establishes-a-red-line-for
[11] https://www.wshblaw.com/experience-benavides-v-tesla-a-defense-side-perspective-on-floridas-landmark-autopilot-verdict
[12] https://www.ruuter.ee/en/chinese-court-rules-drivers-liable-in-semi-autonomous-car
[13] https://researchnow-admin.flinders.edu.au/ws/files/45253343/Law_and_tech_collide_foreseeability_reasonableness_and_advanced_driver_assistance_systems.pdf
[14] https://journals.open.tudelft.nl/ejtir/article/download/3486/3634/9388
[15] https://classic.austlii.edu.au/au/journals/CanLawRw/2021/3.pdf


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