A Navigable Street Is Not an Eligible Operating Zone

What happened

On July 28, 2026, a bill was introduced in the US House of Representatives: the AV Emergency Response Coordination Act. Its origin is not hypothetical risk. It follows a documented pattern of incidents in which autonomous vehicles blocked ambulances and fire trucks, drove into active emergency scenes, failed to recognise safety signals such as cones and flares, stalled during power outages, and obstructed traffic around large public events. A city fire chief, speaking at the bill’s announcement, described vehicles interfering with emergency operations while units were actively working an incident — and robotaxis picking up passengers directly in front of fire stations, blocking ambulance deployment.

The bill’s provisions are procedural: standardised emergency response guides distributed to first responders, a 24/7 hotline with a thirty-second response standard, minimum federal performance standards. And one provision of a different kind — a process for public officials to issue geofence notices, compelling vehicles to avoid a designated area for up to 72 hours during an emergency, with compliance expected within two minutes.

This piece takes no position on the bill. What it examines is what the geofence provision concedes about how these vehicles decide where they may operate.

Navigability was not enough

Not every reported incident has the same technical cause. Some involved failures to recognise visible safety conditions — cones, flares, smoke. Those are perception problems, and perception work will keep addressing them.

But another class of failure remains even when perception performs. The street existed on the map. The route was computable. No standing traffic restriction prohibited entry. Speed, signalling, right-of-way — the operating rules the vehicle was dispatched under were being satisfied. In every mapped and coded sense, the street was navigable.

And yet the street was, at that moment, inside a fire scene. Or an active crime scene. Or a corridor an ambulance needed. Or a district where the power was out and the traffic infrastructure the vehicle’s assumptions depended on had stopped functioning.

In that class of incident, the failure is not a rule violation. Navigability and operating eligibility are different properties. A vehicle may evaluate road geometry, traffic rules, and observable conditions, yet still lack an authoritative and current statement that an incident commander has withdrawn the zone from autonomous operation. Navigability is a property of the map and the traffic code — comparatively stable, verifiable at dispatch. Eligibility, in these cases, includes a component the vehicle has no standing to derive on its own: a public authority’s present decision about a zone — a scene perimeter established eleven minutes ago, an evacuation corridor, an outage district. That state is not observable the way a cone is observable. It is declared.

The world can change between approval and execution. Dispatch establishes that the trip may begin. It does not establish that every zone on the route will remain eligible as the trip continues.

What a geofence notice actually is

Read as a traffic measure, a geofence notice is a temporary road closure. Read structurally, it is something more interesting: an external authority delivering a change of operating-environment state directly into the vehicle’s eligibility calculation — a public decision the vehicle has no authoritative way to infer for itself.

The provision’s parameters make the structure explicit. A notice lasts up to 72 hours: eligibility is suspended for a bounded period, not revoked permanently — the street will be navigable and eligible again. Compliance is expected within two minutes: the gap between the world changing and the vehicle’s behaviour reflecting it is treated as a specified, bounded quantity. That is a propagation deadline for a state change — the kind of parameter that only makes sense once you accept that eligibility is current, external, and perishable.

In other words: the mechanism now proposed in federal legislation is a formal channel for telling an autonomous system that a zone it considers valid is not, at present, an area it is eligible to operate in. The existence of the channel makes the distinction explicit. If dispatch-time validity were sufficient, no such channel would be needed.

The moments that matter

The notice mechanism handles one direction: authority pushing a state change outward. The harder half of the problem sits on the vehicle side, because an emergency does not respect trip boundaries.

Consider when the eligibility question actually needs an answer. Before a route is entered — is any segment of it inside a declared zone? At the moment a zone forms — which vehicles are already inside it, already en route to it, already holding pickups within it? When an emergency vehicle approaches — does a corridor need to open now, regardless of any zone? When communications or power degrade — can the vehicle still receive the state it depends on, and what should it assume when it cannot?

Each of these is a distinct moment at which the environment’s current state must be re-bound to the vehicle’s authority to proceed. A trip checked once at dispatch answers none of them. A zone list refreshed on a polling cycle answers them late — and the two-minute compliance window in the bill is, implicitly, a statement about how late is too late.

The last question — what to assume when the state channel itself fails — is the one the power-outage incidents already answered badly. A vehicle that cannot currently verify the operating environment it depends on is not in a neutral condition. It is in exactly the condition where its dispatch-time assumptions are least trustworthy.

The proposition

The reported incidents and the proposed remedy describe the same gap from two sides.

The relevant incidents show that a valid dispatch and a navigable route can outlive the operating conditions that made movement acceptable. The remedy shows the governing side building a channel to re-bind that environment to the vehicle’s eligibility while the trip is in progress — with an explicit bound on how stale the binding may be.

A navigable street is a fact about the map. An eligible operating zone is a fact about now. The distance between those two facts is where the relevant class of incidents lived — and deciding, at each moment that matters, whether the current environment still supports the movement under way is not merely a mapping or perception problem. It is execution governance, applied to motion.