The Capitol LedgerEvery move in Congress, on the record
HomeBillsRecordsLedger AI

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

AboutFAQFeedbackTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

The projectAboutFAQFeedback
LegalTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

All bills
S. 3536·119th Congress·Introduced Dec 17, 2025

Stay in Your Lane Act

IntroducedTransportation and Public WorksSubstantive
View bill text
Sponsor
Sen. Markey, Edward J. [D-MA]
Committees
Commerce, Science, and Transportation Committee (primary)
Last action
Dec 17, 2025

Bottom line

The "Stay in Your Lane Act" aims to enhance the safety of driving automation systems by requiring manufacturers to clearly define and adhere to the safe operating conditions for their technology, with non-compliance subject to civil penalties.

What it actually does

This bill mandates that manufacturers of driving automation systems (like advanced driver-assistance systems or self-driving cars) must define the "operational design domain" (ODD) under which their systems are designed to function safely. It requires manufacturers to ensure their systems do not operate outside this defined ODD and to publicly declare their ODD definitions to the National Highway Traffic Safety Administration (NHTSA) and on their websites.

Proponents argue

Supporters argue that this bill will increase transparency and accountability for manufacturers of driving automation systems, ensuring that these advanced technologies are deployed and operated only under conditions for which they are proven safe. They contend that clearly defined and publicly available ODDs will help prevent misuse, inform consumers, and provide NHTSA with crucial data for oversight, ultimately improving road safety as automated vehicles become more common.

Opponents contend

Critics might argue that mandating specific ODD declarations and strict adherence could stifle innovation in the rapidly evolving autonomous vehicle sector by imposing rigid regulatory burdens. They may contend that manufacturers already have incentives to ensure safety and that overly prescriptive regulations could slow the development and deployment of potentially life-saving technologies, or that defining ODDs too narrowly could limit the utility of these systems.

The bill is very short and straightforward, making it highly accessible for a quick read and understanding of its core provisions.

Section 2(a)(1), adding new Section 30130 to title 49, United States Code.

Mandating Operational Design Domain (ODD) Definition and Adherence

prominently featuredstraightforward

This provision requires manufacturers of driving automation systems to define the specific operating conditions (like weather, road type, time of day) under which their systems are designed to function safely, known as the Operational Design Domain (ODD). It then mandates that these systems must not operate outside of these manufacturer-defined safe domains.

GroupImpactMechanismScale
GroupDriving Automation System ManufacturersImpactIncreased regulatory burden and liability.MechanismLegal requirement to define and adhere to ODDs, and to submit declarations to NHTSA.ScaleIndustry-wide for all manufacturers of driving automation systems.
GroupConsumers/PublicImpactEnhanced safety and clearer understanding of system limitations.MechanismSystems are restricted to conditions where they are designed to be safe; public access to ODD definitions.ScaleBroad impact on road safety and consumer confidence.

Supporters argue

Supporters argue this provision is crucial for public safety, as it places clear responsibility on manufacturers to define and respect the limits of their technology. It prevents the deployment of systems in conditions they are not designed to handle, reducing the risk of accidents and fostering consumer trust.

Critics contend

Some industry stakeholders might argue that precisely defining and strictly adhering to ODDs could be technically challenging and restrict the flexibility needed for continuous improvement and over-the-air updates. They might also contend that this could lead to overly conservative ODDs that limit the utility of the systems for consumers.

Tradeoffs

The tension lies between ensuring safety through clear boundaries and allowing for innovation and flexibility in a rapidly evolving technological field. While strict ODDs enhance safety, they could potentially slow down the development and broader adoption of advanced features.

Section 2(a)(1), new Section 30130(c) of title 49, United States Code.

Public Transparency of ODD Definitions

prominently featuredstraightforward

This provision requires manufacturers to submit their defined Operational Design Domain (ODD) declarations to the National Highway Traffic Safety Administration (NHTSA) and to make the exact same declarations publicly available on their company websites. This ensures that both regulators and the public have access to the official safe operating parameters of these systems.

Section 2(b) and 2(c) of the bill, amending Sections 30165(a)(1) and 30102(b) of title 49, United States Code.

Civil Penalties and Regulatory Authority for ODD Compliance

mentioned in summarymoderately complex

This provision integrates the new ODD requirements into existing federal motor vehicle safety law. Specifically, it makes violations of the ODD adherence mandate (operating outside the defined domain) subject to civil penalties. Furthermore, it explicitly includes the ODD definition and declaration requirements within the definition of a "motor vehicle safety standard," granting NHTSA clear authority to regulate and enforce these provisions.

FOUND

The Act and its amendments take effect 180 days after the date of enactment.

Section 2(d)

Why it matters:Standard legislative practice to place effective dates at the end.

Case for: Provides manufacturers a reasonable grace period to comply with the new requirements, allowing time to define ODDs, update systems, and establish public declaration processes.

Case against: Critics might argue that a 180-day delay is too long given the urgency of ensuring safety in rapidly deploying technologies, or too short for complex systems requiring significant re-engineering.

Estimated impact: Provides a clear timeline for implementation, impacting when the regulatory changes become enforceable.

About this analysis. AI-Generated from the official bill text and available committee reports. Gaps in available data are noted explicitly. Verify important details with the official Congress.gov record.

On this page

  • Executive summary
  • Key provisions
  • Buried treasure
  • Follow the money
  • Critical analysis
  • Questions to ask
Ask Ledger AI about this