Delivery-robot safety is often communicated through total delivery counts or a short statement that
incidents were minor. Neither measure is sufficient on its own. Twenty-seven thousand completed
deliveries demonstrate real use, but seven incidents cannot be judged without exposure: autonomous
kilometres, operating hours, missions, pedestrian encounters and remote interventions. A programme
can therefore appear successful to an operator while remaining opaque to the authority deciding
whether it should continue.
Regulatory observability means designing the fleet to produce understandable, auditable evidence
continuously. Incident counts should be normalized per 1,000 missions or kilometres. Obstruction
duration, accessible-clearance violations, clustering, emergency stops and field-response time should be
recorded alongside collisions. Privacy rules must define what camera evidence is retained, who can
access it and for how long. This changes compliance from a last-minute report into a normal product
function.
Fainzy’s way forward
Fainzy should apply and monitor this approach before ZiBOT enters public space. The fleet manager
should generate weekly authority reports automatically, while the autonomy stack logs minimal-risk
stops, intervention causes and fleet-level congestion. In early Indian and Japanese pilots, this evidence
can help customers, regulators and property operators widen the operating domain with confidence.