Botz Group Botz GroupBotz GamesBotz VenturesGord HoldingsGord CapitalGord EnterprisesMichael GordMetaverse GroupMetaverse VenturesMetaverse PropertiesMetaverse CasinoFlashy GroupFlashy OSFlashy IDFlashy GoldFlashy NetworkFlashy AcademyClaim Your GoldFlashy LabsMagicianRite ProtocolRitualOSFlashy FunFlashy SocialFlashy FinancialGDA GroupMLG Blockchain4.venturesNFT Capital Part of Gord Holdings
botzgroup.co
Answer · as at 2026-08-28

Who is liable when a robot causes harm?

The answer

Liability for a robot falls on whoever authorised it to act — but establishing that requires the authorisation to have been recorded at the time, to have been narrower in scope than the authoriser's own permissions, and to be revocable in a way that demonstrably stops the machine. Most robots deployed today record none of those three things, so liability falls back to the site operator by default rather than by design.

§ 01

The working

Why "the operator is liable" is a symptom

Site operators carry robot liability not because anyone decided they should, but because there is nothing else to attach it to. The machine has no identity, the deployment has no recorded grant, and the telemetry records what happened rather than what was permitted. An investigator asking who allowed this finds a configuration file and a contract.

What would have to exist instead

A grant issued at a moment, to a named scope, by a named principal, revocable and testably so. That is not a novel requirement — it is the ordinary structure of delegated authority in software, and the reason it is absent from robotics is that the two fields have been separate industries rather than that the artefact does not fit.

The insurance consequence

Insurers price what they can characterise. A machine whose permitted actions were never recorded cannot be distinguished, after an incident, from one acting outside its remit — so the premium reflects the worst case. Recorded, attenuating, revocable authority is not a compliance nicety; it is the difference between an insurable and an uninsurable deployment.

Sources: NIST — least privilege · ISO 10218 — industrial robots, safety requirements. Dated 2026-08-28; superseded by publishing a new answer, never by editing this one.