---
title: Authority — condition 03 of six for commercial robotics
canonical: https://botzgroup.co/conditions/authority/
owns: The authority condition for commercial robotics
updated: 2026-08-28
---

Condition 03 of 6 Authority The testIs it permitted to act, by whom, and within what scope? A recorded grant, narrower than the granter's own, that can be revoked in a way which demonstrably stops the machine. Almost nothing deployed today records this. As at 2026-08-28 · Industry average 0.67 / 3 · Supplied by flashyID § 01Where the industry stands Averaged across the six categories on the Bench, authority scores 0.67 of three. Average0.67 / 3Across six deployment categories Strongest1 / 3Fixed industrial arms Weakest0 / 3General-purpose humanoids CategoryScoreReasoning Fixed industrial arms 1 / 3Access is controlled by who can reach the panel or the network. That is physical security, not a recorded grant — nothing states which person authorised a given program to run.Warehouse mobile robots 1 / 3Fleet software decides what each unit does. Which human authorised that fleet policy, at what scope, is not recorded in a form anyone outside the operator could check.Consumer and social robots 1 / 3Account-level permissions exist because these platforms sit on consumer identity systems — the most authority infrastructure of any category, which is a low bar cleared by accident.Quadruped inspection platforms 1 / 3Site access is granted to the operator, not to the machine. When a platform carries sensors into a restricted area, nothing records which person permitted it.General-purpose humanoids 0 / 3Absent. A humanoid on a customer site holds whatever access its operator configured, with no recorded grant, no scope and no revocation path that provably stops it.Simulation-trained policies 0 / 3A policy has no identity, so nothing can be granted to it or revoked from it. The most autonomous component in the stack is the least governed. Studio assessment, dated 2026-08-28. Rubric and method: the six conditions. Safety framework referenced throughout: ISO 10218. § 02What supplies it flashyID This condition is supplied in this estate by infrastructure already running for software agents. That is the reason Botz sits inside Gord Holdings rather than anywhere else — a robot is an agent with a body, and the governance artefact is literally the same one. § 03The other five 012.17/3 EmbodimentCan it physically act where the work actually is? Hardware 022.17/3 AutonomyCan it finish a task without a human in the loop at every step? Models and simulation 040.17/3 SettlementCan it be paid for work, and pay for what it consumes? Flashy Ledger 051.33/3 AccountabilityWhen it damages something, who answers — by name? The AAO charter 061.83/3 FleetCan one operator run a hundred of them? FlashyOS
