uniteTOlove.ca

Automated/Autonomous-Vehicle Policy

Self-driving cars are already being piloted on Ontario roads — who regulates them and how safety is actually checked.

DRAFTThe evidence file

Claim coverage as of 2026-07-22: 41 formally registered claims cited (28 verified / 13 still being checked / 0 disputed / 0 removed as unverifiable) · Coverage: breadth not formally checked in this review. This draft establishes claim-level coverage against the claims register only; a breadth comparison against master briefing/v1-reference equivalents (the actual breadth check) is not attempted here and is not asserted as passed or failed. Cui Bono: 0 beneficiary entities identified (0 ESTABLISHED / 0 REPORTED) — see "Cui Bono" section below for why.

First drafted this review (2026-07-22) against a parallel-lane draft already present in the working tree; per this review's ownership discipline (never blind-merge), the drafting session independently re-verified the full document before landing it as canonical rather than adopting it on trust or on a sampled check alone: (1) a programmatic script cross-checked the claim-index appendix against prose citations in both directions — 41/41 claims for this slug cited, appendix and prose sets identical, zero claims from another issue slug's topic tag cited; (2) a firewall grep for named individual officials and local filesystem paths returned clean; (3) five claim citations were manually diffed against their exact the claims register text and matched verbatim/near-verbatim; (4) the International-context and polling-section external facts (UNECE 1998 Agreement/Canada's contracting-party status, Transport Canada's UN GTR consultation window, California DMV's April 2026 rulemaking, UK Automated Vehicles Act 2024, Singapore LTA/TR-68, and the Leger/Rates.ca April 2026 survey figures) were independently re-searched this review and found accurate to the draft's claims. No content changes were needed as a result of this review — the draft is landed as-is.

Scope

This backgrounder's neutral scope question, per this library's issue index row G1: "How are automated/autonomous-vehicle pilots and related road-automation technology regulated, permitted, and safety-monitored?" Owner column: provincial (MTO's Automated Vehicle Pilot Program, O. Reg. 306/15); municipal (road/right-of-way permitting, transit-integration decisions).

G1 is one of four "a later round" ratified additions (G1–G4, 2026-07-19) mapping to the V2 program family AUTOMATA. Per this library's issue index's own note on that addition, these G-series rows are scoped narrowly to the concrete, institutionally-checkable municipal/civic angle inside each program's much broader mission — the program charter (this library's internal planning records/) remains the source of record for the movement/visionary material, and this document does not absorb or restate that scope. This document covers only the regulatory, permitting, and safety-monitoring facts this claims register has independently verified.

This document covers: the division of AV regulatory authority across federal, provincial, and municipal governments; the mechanics and permitted vehicle classes of Ontario's Automated Vehicle Pilot Program (O. Reg. 306/15) and its 2025 sibling, the Automated Commercial Motor Vehicle (ACMV) Pilot Program for heavy trucks; safety-monitoring, reporting, and liability requirements at both federal and provincial levels; Toronto's own AV planning and the specific pilots run under it; private-sector AV activity and pending applications in Ontario and British Columbia; and comparative material from Quebec, British Columbia, and select international jurisdictions.

It does not cover, and hands off by name: general pedestrian/cyclist collision counts and traffic-calming measures (road-safety-vision-zero, B2), except where a claim about AV testing itself documents a collision-reporting obligation; on-street/off-street parking supply and pricing generally (parking-policy-management, B4), except where a claim is specifically about AV parking behaviour; and broader transit service levels, fares, and municipal transit-integration planning (mobility-congestion-transit, B1★, and regional-transportation-integration), which this document does not duplicate even though AV shuttle pilots touch transit.

Current state

Jurisdictional division of authority

Automated-vehicle regulation in Canada divides across three levels of government along a documented, consistent pattern. Transport Canada, through the Motor Vehicle Safety Act, regulates the safety of manufactured and imported vehicles and interprovincial vehicle shipment; provinces and territories are responsible for licensing drivers, vehicle registration and insurance, and for approving and overseeing on-road automated-vehicle trials within their own jurisdiction; municipalities are responsible for enacting and enforcing local bylaws and managing local infrastructure and passenger transportation [CL-100036]. An independently authored legal-analysis source describes the same division in near-identical terms: automated-vehicle technology and testing is a shared responsibility between the federal and provincial/territorial governments, with provinces and territories regulating individual drivers and vehicle operation and the federal government, through Transport Canada, setting safety regulations for vehicles sold or imported into Canada [CL-100044]. Where a province imposes requirements additional to or different from Transport Canada's own federal testing guidelines, the province's own requirements prevail and must be followed by the trial organization [CL-100038].

This division has a documented practical consequence for municipal authority specifically. When Ontario's Ministry of Transportation approved an application from New Mobility Canada Delivery Systems Inc. (an operating entity of Magna International) to test automated last-mile delivery vehicles on Toronto's streets in April 2025, the City of Toronto had no regulatory authority over the pilot under Ontario Regulation 306/15, though the Ministry invited City staff to review the application and submit comments [CL-100028].

Ontario's Automated Vehicle Pilot Program: mechanics, permitted technology, and scale

Ontario's Automated Vehicle Pilot Program, under Ontario Regulation 306/15, began in 2016 and was updated in 2019, in response to developments in automated-vehicle technology, to allow for the testing of driverless automated vehicles and cooperative truck platoons under certain conditions [CL-100024]. The pilot has since been extended to October 13, 2027, rather than lapsing at its original ten-year mark [CL-120011]. Under the pilot and the Highway Traffic Act, the public may drive a commercially-available SAE Level 3 vehicle, while Level 4 and Level 5 vehicles are permitted only for authorized applicants for testing purposes, who are subject to additional reporting and record-retention obligations [CL-100043] — obligations that include accepting full liability, disclosing the vehicle's operational design parameters, being able to bring the vehicle to a safe stop, providing a work-zone and first-responders' interaction plan to affected authorities, notifying affected municipalities before testing begins, and displaying signage identifying the vehicle as a driverless automated vehicle being tested [CL-100027]. As of a 2025 City of Toronto staff report, the program had had 14 approved participants since its 2016 launch, spanning passenger vehicles, low-speed shuttle services, and light-duty commercial vehicles [CL-100030].

Safety-monitoring, reporting, and liability requirements

Participants in Ontario's pilot must carry a minimum of $5 million in automobile liability insurance coverage, or $8 million for vehicles with a seating capacity of eight or more passengers [CL-100025], must provide an annual report with testing information, and must report any collision within 10 days of the incident [CL-100026]. At the federal level, Transport Canada's Safety Assessment for Automated Driving Systems in Canada identifies 13 safety outcomes that trial organizations are encouraged to address in a safety assessment report, including the system's level of automation and intended use, its Operational Design Domain, Object Event Detection and Response capabilities, cyber security, and user privacy [CL-100037]. Canada's federal Motor Vehicle Safety Act was amended in 2018 to add limited exemptions for automated vehicles meeting certain standards [CL-100046], and a new administrative monetary penalty regime developed following those amendments came into force on October 3, 2023 [CL-100041]. Transport Canada's Motor Vehicle Safety Oversight Program more broadly conducts or manages more than 20,000 oversight tasks each year across all regulated vehicles — inspecting and testing regulated vehicles, tires, and equipment; reviewing companies' certification documentation; investigating potential safety defects; and monitoring vehicle recall campaigns [CL-100042] — a program-wide baseline noted here for context, not a figure specific to AVs alone.

The insurance industry has itself recommended changes to this framework: the Insurance Bureau of Canada's report on auto insurance for automated vehicles recommends establishing a single insurance policy covering both driver negligence and automated technology, a legislated data-sharing arrangement between vehicle manufacturers, owners, and insurers to help determine the cause of a collision, and updated federal vehicle safety standards addressing technology and cybersecurity [CL-100045] — cited here as the Bureau's own stated recommendation, not adopted as this document's position.

Ontario's new Automated Commercial Motor Vehicle Pilot Program (2025)

In 2025, Ontario launched a new Automated Commercial Motor Vehicle (ACMV) Pilot Program, distinct from the passenger-oriented Automated Vehicle Pilot Program above, allowing testing of truck configurations weighing more than 4,500 kg that meet the SAE International standard for Level 3, 4, or 5 autonomy; the program runs until August 1, 2035 and allows either driver-supervised or driverless testing [CL-100047]. Participants moving from the driver-supervised testing stream to driverless testing must first complete a minimum of 100,000 km of testing in North America and two years of testing in Ontario under the driver-supervised stream, and demonstrate proof of concept within the same testing environments [CL-100048] — a requirement corroborated independently by Ontario's own program-conditions page, which additionally specifies that driverless-stream participants must maintain a minimum of $10 million in public liability insurance coverage [CL-140615, “still being checked”]. Participating vehicles must display "TEST VEHICLE – STAY BACK" signage, carry an on-board device recording speed, time, and date, and notify authorities within 24 hours of any collision or other incident [CL-140617, “still being checked”]. Ontario's Ministry of Transportation states it will collect performance data under the ACMV pilot specifically to assess how automated trucks function with minimal driver involvement, compared against conventional vehicles on safety, efficiency, and reliability [CL-140618, “still being checked”].

The government's own Regulatory Registry posting proposing the ACMV framework, ahead of the program's official launch, states the program imposes no new regulatory costs or burdens on participating stakeholders, and describes a proposed 10-year pilot duration [CL-140616, “still being checked”] — consistent with the enacted program's stated end date of August 1, 2035, roughly a decade from its 2025 launch [CL-100047].

Toronto's municipal AV planning and deployed pilots

Beyond the province's own regulatory framework, Toronto has run its own AV planning process since at least 2019. The City's 2019 Automated Vehicles Tactical Plan set an "AV Ready by 2022" near-term strategy comprising five projects: an automated shuttle trial, implementing zones for transportation innovation, developing AV testing response and incident preparedness (TRIP) protocols, undertaking public education initiatives, and furthering research and development [CL-100032]. The Plan is organized around seven strategic directions and 18 goals for the year 2050, translated into 78 tactics with a proposed level of progress to be reached over the following three years [CL-100033], and was developed under the leadership of the City's Interdivisional Working Group on Automated Vehicles, comprising staff from 30 City divisions and agencies [CL-100034].

Several specific pilots have run under this planning framework and the provincial program it operates alongside. A 2025 City of Toronto staff report lists, among prior Ontario AV pilots: the WATonoBus shuttle at the University of Waterloo (began 2021, a 2.7 km campus route carrying up to 10 passengers); the Whitby Autonomous Vehicle Electric (WAVE) shuttle (2021), which ended after a collision while operating in manual mode; Toronto's own West Rouge Automated Shuttle Trial (two months of validation and testing in late 2021 on a four-kilometre route), which ended before public service began; and Gatik's driverless grocery-delivery trucks for Loblaw in Peel Region, which completed more than 150,000 autonomous deliveries with a safety driver on board between January 2020 and October 2022 [CL-100031]. The most recent named pilot is Magna's automated last-mile delivery vehicle (LMDD) project, approved by MTO in April 2025 [CL-100028]: it operates at a maximum speed of 32 km/h on roads with a posted speed limit of 40 km/h or less, does not make left turns, and requires both a human "chase vehicle" supervisor following the vehicle and a remote operator able to assume control; Magna carries the $5 million per-incident liability insurance required under the Highway Traffic Act and had requested a permit for up to 20 vehicles during the pilot [CL-100029].

Federal safety framework, program support, and stated rationale

Transport Canada and the Canadian Council of Motor Transport Administrators (CCMTA) published a first Guidelines for Testing Automated Driving Systems in Canada in 2018, agreed upon by federal, provincial, and territorial representatives [CL-140619, “still being checked”]; this was formally superseded by Version 2.0 in 2021, developed in the same consultative process, applying to any organization conducting research and development trials of ADS-equipped vehicles at SAE Levels 3 to 5 in Canada [CL-100035]. Transport Canada separately runs the Program to Advance Connectivity and Automation in the Transportation System (ACATS), which supports research and technology evaluations, the development of codes/standards/guidance materials, and capacity-building and knowledge-sharing activities intended to help prepare Canada for wider use of connected and automated vehicles on its roads [CL-140643, “still being checked”]. Ontario funds AV-adjacent research and commercialization provincially through the Ontario Vehicle Innovation Network (OVIN), the government's funding successor to the earlier Autonomous Vehicle Innovation Network (AVIN); OVIN supports connected/autonomous and electric-vehicle technology commercialization, backed by an additional $56.4 million in provincial funding for a cumulative total investment of over $141 million to date [CL-140636, “still being checked”].

Federal materials frame this regulatory effort against a stated road-safety and economic rationale. Transport Canada reports that in 2022, 1,931 people died on Canada's roads, with human behaviour a contributing factor in around 85% of fatal collisions; the leading human-behaviour contributing factors in fatal collisions were impairment (23%), speeding (20%), and distraction (20%) [CL-100039]. Transport Canada separately estimates the social and economic cost of motor vehicle deaths and injuries in Canada at approximately $40 billion in 2021, roughly 2% of the country's gross domestic product [CL-100040]. These figures describe the general road-safety context Transport Canada's own materials cite alongside its automated-vehicle program; the claims register does not currently contain a claim directly linking AV deployment in Canada to a measured reduction in either figure (see "Open questions / data gaps" below).

Private-sector AV activity and pending applications

Independent of the pilot programs themselves, Ontario has seen active private-sector AV development and expressed interest from external operators. Waabi Innovation Inc., a Toronto-headquartered autonomous-vehicle company founded in 2021, has publicly launched its self-driving system for long-haul trucking, operating trucks with human safety drivers and safety engineers on board as the technology continues development [CL-100049]; the company raised US$83.5 million in a funding round backed by investors including Uber Technologies Inc. and Aurora Innovation Inc. [CL-100050].

Separately, Waymo — a US-based autonomous-vehicle operator — has shown developing interest in both Ontario and British Columbia. As of December 2025, Waymo had joined Toronto's lobbyist registry seeking regulatory frameworks for autonomous ride-hailing in Canada, but the City of Toronto stated that no discussions about Waymo operating in Toronto had begun, and the lobbyist registry showed no communications between lobbyists and the city to date [CL-140641, “still being checked”]. By April 2026, Waymo had indicated to the Toronto mayor's office that it intends to apply to Ontario's Automated Vehicle Pilot Program to conduct testing and demonstrations in the city [CL-140640, “still being checked”]. In British Columbia, as of March 2026, Waymo had been lobbying the provincial government to change its regulations to permit the company's fully autonomous taxi service to operate in the province, while BC's rules continued to prohibit Level 3 and higher automated vehicles on public roads [CL-140642, “still being checked”].

Interprovincial comparison: Quebec and British Columbia

Ontario's approach is one of several distinct provincial regimes operating under the shared federal testing-guidelines floor described above. Quebec's autonomous bus and minibus pilot project, jointly overseen by the province's transportation ministry and the Société de l'assurance automobile du Québec (SAAQ), assesses vehicles at SAE automation level 3, 4, or 5, and includes completed trials in Candiac (2019) and two trials in Montreal (2019 and 2021–2022) [CL-140637, “still being checked”]. British Columbia has taken a more restrictive baseline approach: its Motor Vehicle Act, amended effective April 5, 2024, prohibits driving or permitting the driving of a Level 3, 4, or 5 automated vehicle on public roads unless authorized through a pilot project or future regulation, with penalties ranging from $368 and 3 driver penalty points up to $2,000 and six months' imprisonment [CL-140638, “still being checked”] — a prohibition independently corroborated by contemporary news coverage of Waymo's BC lobbying effort, above [CL-140642]. Ontario's own regime sits between these two models in one specific respect: it permits public driving of a commercially-available Level 3 vehicle outright, while restricting Level 4/5 operation to authorized testing [CL-100043] — a more permissive baseline for Level 3 specifically than BC's blanket prohibition, though no claim in this set characterizes which province's overall regime is more or less permissive in aggregate across all levels and use cases.

Research evidence on AV traffic effects: the Toronto parking study

One academic study in the claims register examines a specific behavioural effect of AV deployment on Toronto's own road network, independent of the regulatory pilots above. A 2021 peer-reviewed simulation study of autonomous-vehicle parking behaviour in downtown Toronto found that AVs would travel an average of 12 minutes and a maximum of 47 minutes to reach cheaper parking, and that a toll on zero-occupant AVs would reduce vehicle-kilometres-travelled in downtown Toronto by 3.5% [CL-140639, “still being checked”]. This is a single, not-yet-independently-corroborated modelling study, not empirical measurement of any deployed pilot's actual traffic effect, and it is the only claim in this set addressing potential AV impacts on congestion or parking demand specifically.

Key tensions / tradeoffs

Municipal planning ambition versus municipal regulatory authority. Toronto set an "AV Ready by 2022" strategy in its own 2019 Tactical Plan, including developing incident-preparedness protocols and public-education initiatives [CL-100032], under a City-wide Interdivisional Working Group spanning 30 divisions [CL-100034]. But when Ontario's Ministry of Transportation approved the Magna last-mile-delivery pilot for Toronto's own streets in 2025, the City had no regulatory authority over that pilot under O. Reg. 306/15 — the Ministry only invited City staff to review the application and comment [CL-100028]. This is a documented tension between a municipality's own stated readiness planning and the province's retained approval authority over which AVs actually operate on that municipality's streets; both halves are drawn from the City's own account (its 2019 plan and its 2025 staff report), not from an adversarial second source.

Stated no-added-burden framing versus documented compliance obligations. Ontario's own Regulatory Registry posting proposing the ACMV framework states the program "imposes no new regulatory costs or burdens on participating stakeholders" [CL-140616, “still being checked”]. Set against that framing, the enacted program's own conditions require driverless-stream participants to carry a minimum of $10 million in public liability insurance [CL-140615, “still being checked”], complete 100,000 km of North American testing and two years of Ontario testing before progressing to driverless operation [CL-100048], display specific signage, carry an on-board recording device, and notify authorities within 24 hours of any incident [CL-140617, “still being checked”]. Both descriptions are drawn from government sources describing the same program at different stages (pre-launch proposal versus enacted conditions); this document notes both without asserting the "no new burden" framing is inaccurate — a regulatory proposal's own no-added-cost framing is often assessed relative to a specific existing baseline that the current claim set does not itself specify.

Interprovincial regulatory divergence on the same underlying vehicle classes. Ontario permits public driving of a commercially-available SAE Level 3 vehicle outright, restricting only Level 4/5 to authorized testing [CL-100043]. British Columbia's Motor Vehicle Act instead prohibits driving or permitting the driving of a Level 3, 4, or 5 automated vehicle on public roads absent pilot authorization, with penalties up to $2,000 and six months' imprisonment [CL-140638, “still being checked”]. Quebec runs its own province-specific assessed pilot program for buses and minibuses at the same SAE levels [CL-140637, “still being checked”]. All three provinces operate nominally under the same federal testing-guidelines floor [CL-100035, CL-100038], but have chosen materially different baseline permissiveness for the identical SAE automation-level taxonomy — a genuine, evidenced divergence rather than a mining gap, since all three provincial positions are independently and specifically sourced.

What the evidence does and doesn't support

Well-supported (independent sources converging on the same conclusion):

Thin or contested:

International context

1. Treaties/frameworks touched. Unlike a human-rights-anchored issue such as housing, this issue's genuine international connection is a technical vehicle-standards framework rather than a UN human-rights instrument. Canada is a signatory to the 1998 Agreement Concerning the Establishing of Global Technical Regulations for Wheeled Vehicles, Equipment and Parts, administered through the UN Economic Commission for Europe's World Forum for Harmonization of Vehicle Regulations (UNECE WP.29); under that Agreement, if the UN adopts a Global Technical Regulation (GTR) on automated driving systems, Canada must develop national regulations incorporating all or part of it. Transport Canada's own public consultation page on the UN GTR on Automated Driving Systems describes the proposed regulation as covering a safety-management-system requirement for developing automated driving systems, performance requirements for the "dynamic driving task," a safety-case submission process, and monitoring/reporting/oversight requirements, and states Transport Canada sought stakeholder input (accepted through May 1, 2026) on the GTR's compatibility with existing Canadian motor vehicle law (Transport Canada, "The United Nations Global Technical Regulation on Automated Driving Systems," consulted 2026-07-22). UNECE itself announced adoption of what it describes as the first global regulatory framework for fully driverless automated driving systems, with Canada named among the major markets (alongside China, the EU, Japan, the UK, and the US) endorsing it (UNECE press release, "UNECE adopts first-ever global rules allowing fully autonomous vehicles," 2026; corroborated by Electric Autonomy Canada's contemporary coverage). No claim in this issue's claims register set currently documents Ontario's or Toronto's own specific engagement with this GTR process — this document names the connection as real and found via this review's own search, distinct from and not yet promoted into a registered claim row (see "Open questions / data gaps" below).

2. Best global comparators. Three jurisdictions surfaced in this review as the most concretely comparable, evidenced regulatory models: California's Department of Motor Vehicles operates the most heavily documented AV permitting regime among US states — a phased structure requiring a manufacturer to hold a permit for testing with a safety driver before it can obtain a Driverless Testing Permit, and then a Deployment Permit, each stage gated on completing the prior one; regulations finalized April 28, 2026 extended this framework to heavy-duty vehicles over 10,000 pounds (previously excluded) and, effective July 1, 2026, allow law enforcement to issue a "notice of autonomous vehicle noncompliance" that a manufacturer must respond to within 72 hours (California DMV, "California Autonomous Vehicle Regulations," and Covington & Burling / Sidley legal-analysis coverage of the April 2026 rulemaking). As of that coverage, 27 companies held California AV testing permits. The United Kingdom's Automated Vehicles Act 2024 takes a structurally different approach to liability rather than permitting mechanics: it establishes a "self-driving test" a vehicle must pass for authorization, and shifts civil and criminal liability for the vehicle's actions, while a self-driving feature is engaged, away from the vehicle's human occupant and onto the vehicle's licensed operator or manufacturer — underpinned by a statutory statement of safety principles requiring AV safety to be at least equivalent to a careful and competent human driver (Automated Vehicles Act 2024, per Hogan Lovells and Addleshaw Goddard legal-analysis summaries; UK Parliament, legislation.gov.uk). Singapore's Land Transport Authority (LTA) administers AV testing through a "Regulatory Sandbox" under the Road Traffic (Autonomous Motor Vehicles) Rules 2017: an opt-in permit process requiring risk assessments and pre-approved routes before any road deployment, layered with Singapore's Cybersecurity Act 2018 and Personal Data Protection Act compliance obligations, and supported by a national technical-reference standard (TR 68) for AV development (LTA program materials, per Herbert Smith Freehills Kramer and PDLegal legal-analysis coverage). None of these three comparators' own claimed safety or adoption outcomes were independently verified in this review beyond what the cited legal-analysis and government sources themselves state — they are named here as documented regulatory designs, not as proven-successful models.

3. What Toronto/Ontario can steal shamelessly. Stated descriptively, not as a recommendation: (a) California's staged permit progression (safety-driver testing → driverless testing → deployment, each gated on completing the prior stage) is the same design logic Ontario's own newest program already uses — the ACMV Pilot Program's own requirement that a participant complete 100,000 km of North American testing and two years of Ontario testing under supervision before progressing to driverless operation [CL-100048, CL-140615] is a comparable staged-graduation mechanism already present in Ontario's regulatory toolkit, not an untried import. (b) The UK's statutory shift of civil/criminal liability onto a vehicle's licensed operator/manufacturer once a self-driving feature is engaged is a materially different liability-allocation design than Ontario's current model, which instead requires the pilot participant/operator to carry fixed minimum liability insurance directly [CL-100025, CL-140615] — named here as an available alternative design, not as something Ontario should adopt. (c) Singapore's requirement that an AV operator submit pre-approved routes and a risk assessment before any road deployment parallels — without being identical to — Ontario's own existing driverless-testing conditions requiring disclosure of the vehicle's operational design domain and a work-zone/first-responder interaction plan [CL-100027], suggesting the route/risk-assessment framing is one existing point of convergence across jurisdictions rather than a novel import.

What do Torontonians & Ontarians think?

No Ontario- or Toronto-specific public-opinion polling on automated/autonomous-vehicle policy was located in this review. A second, targeted search for Toronto- or Ontario-specific polling on Waymo or robotaxi deployment specifically also returned no polled measurement — only news coverage of the underlying regulatory and lobbying activity already covered above [CL-140640, CL-140641, CL-140642], which documents institutional and corporate activity, not measured public opinion.

The nearest available adjacent measurement is national, not Toronto- or Ontario-specific: a Leger online-panel survey commissioned by Rates.ca, fielded April 17–20, 2026 among n=1,521 Canadian residents aged 18 and older (weighted by age, gender, mother tongue, region, education, and presence of children; margin of error stated by the pollster as ±2.5%, 19 times out of 20), found that only 13% of Canadians surveyed would consider purchasing an autonomous vehicle in the next two years, with 65% not interested; of those not interested, 61% said they wouldn't feel safe in one, and separately 52% of all Canadians surveyed said they mistrust full self-driving mode (Leger/Rates.ca, "Try before you buy: Canadians choose autonomous vehicles as a service before ownership," April 2026). This is a single national measurement, not corroborated by a second poll in this review, and it measures interest in personal AV ownership specifically — a different question from support for, or opposition to, the pilot-program regulatory framework this backgrounder otherwise documents. It is presented here as the nearest adjacent measurement, not as an Ontario- or Toronto-specific finding, per this section's own discipline against stretching an adjacent poll past its actual question.

Cui Bono — who profits from this problem persisting

Per the Accountability Observatory's charter (Prime Rule: pointer, never author) and this library's standard page structure's binding requirement: 0 beneficiary entities identified in this review (0 ESTABLISHED / 0 REPORTED). A direct check against this library's internal records, the accountability register's entities table, and the accountability register's claims table for AV/automated-vehicle/robotaxi/autonomous-trucking-adjacent material found one row that is topically adjacent but out of this issue's scope, and one bare, unlinked entity-register stub with no graded finding attached — neither qualifies as a beneficiary row here.

The adjacent-but-out-of-scope row is ACL-0015 (entity ENT-0015, Verra Mobility Corporation / Redflex Traffic Systems (Canada) Limited), a REPORTED-grade finding describing that company's automated speed-enforcement camera contract with Toronto and its lobbying registration ahead of Ontario's ban on automated speed enforcement. This concerns automated roadside-enforcement technology (speed/red-light cameras) — a different technology and a different issue slug from automated vehicles (self-driving cars/trucks). The two share the word "automated" but are not the same regulatory or commercial question, so this document does not treat ACL-0015 as an AV-policy beneficiary finding.

The unlinked stub is ENT-1230 (Waymo LLC), a bare entity-register row created via a mechanical entity-resolution import pass (2026-07-17) with no accountability_claim_id, no provenance grade, and no beneficial-ownership or financial-relationship finding attached to it — a raw registration, not a graded finding, and therefore not citable as a Cui Bono row under this template's rules. No source checked in this review names any entity profiting specifically from Ontario's or Toronto's automated-vehicle regulatory framework, its pilot-program structure, or its permitting process at an ESTABLISHED or REPORTED grade. This is consistent with the issue having been newly ratified into the claims register's tracked-topics vocabulary (2026-07-19) with no dedicated accountability-mining pass yet run against it — flagged as a genuine gap in "Open questions / data gaps" below, not asserted as evidence that no such beneficiary exists.

Open questions / data gaps

Not yet mined:

Found but not yet formally registered (“still being checked”, cited as such rather than upgraded):

Genuinely uncovered:

Claim-index appendix

Format: claim_id · verification status · one-clause gist, grouped by the section that cites it. A claim cited in more than one section is listed once per section, matching how it is actually used in the prose above.

Scope — no claims cited (framing section only, per template).

Current state — Jurisdictional division of authority

Current state — Ontario's Automated Vehicle Pilot Program

Current state — Safety-monitoring, reporting, and liability requirements

Current state — Ontario's new ACMV Pilot Program (2025)

Current state — Toronto's municipal AV planning and deployed pilots

Current state — Federal safety framework, program support, and stated rationale

Current state — Private-sector AV activity and pending applications

Current state — Interprovincial comparison: Quebec and British Columbia

Current state — Research evidence on AV traffic effects

Key tensions / tradeoffs

What the evidence does and doesn't support

International context / Cui Bono

What do Torontonians & Ontarians think

About this file

Domain: Cross-cutting — G1/AUTOMATA program family (ratified addition, 2026-07-19; no MCI four-domain assignment in `this library's issue index`)