Street-level automation is easy to describe as a hardware problem. In practice, every vehicle or service robot needs a defined operating area, a clear relationship to people on foot, and an accountable operator.
Delivery robots, low-speed shuttles, and other automated services may interact with sidewalks, loading zones, campuses, crossings, and curbs. Their design choices affect accessibility and daily movement: where they wait, how they yield, which routes they use, and how a resident can report a problem.
Cities can assess these systems as users of public space, rather than as isolated technology demonstrations. Pilot rules can state operating zones and hours, speed limits, insurance, maintenance duties, accessible clearances, incident reporting, and a responsible point of contact. A clear operating envelope helps both residents and operators understand what service is being tested.
Operational measures should be specific to the public purpose. Trip counts alone say little about whether a service works. Cities can also track delivery reliability, blocked-path reports, near-misses, service availability, and impacts across neighborhoods. Data collection should be limited to what evaluation needs and handled with appropriate privacy safeguards.
The practical test is whether automation fits the street people already use. That means planning for access, accountability, and service outcomes alongside the device itself.