The velocity authority problem: accountability when physical autonomous systems must decide before authority can be confirmed

A drone identifies an obstacle at 40 metres. At its current airspeed it has roughly 200 milliseconds to initiate avoidance. The minimum round-trip latency to a remote command centre is 400 milliseconds. The principal hierarchy — the chain of authority from which the drone derives permission to act — is, in this moment, physically unreachable. The math does not close.

This is the velocity authority problem: the gap between the time a physical autonomous system needs to decide and the time its authority framework requires to confirm that decision is authorised. It is not a bandwidth problem. More spectrum does not solve it. It is a structural property of physical AI, and it breaks the "check first" accountability model that most agent governance frameworks assume.

The structural asymmetry

Software agents have a privilege physical agents do not: they can pause. An agent unsure of its authority can hold, log the uncertainty, and escalate. The state it was reasoning about may persist while review happens. The cost is delay; the benefit is oversight.

Physical agents operating in the world often cannot pause without the pause itself becoming consequential. A drone that holds before an obstacle does not hover; it continues on its current trajectory. An autonomous vessel waiting for authorisation during a collision avoidance decision is not waiting — it is committing to an outcome. In high-velocity physical systems, the absence of a decision is a decision. The accountability framework must account for this.

The post-quantum security crossing

The problem sharpens when authentication must be quantum-resistant. Post-quantum cryptographic schemes add latency relative to classical signatures. For a physical system that must respond in tens of milliseconds, a post-quantum authentication round-trip is not just inconvenient — it creates a structural incentive to bypass the check entirely.

This is the asymmetry the post-quantum transition introduces for physical AI: the systems that most need strong identity guarantees — those taking irreversible physical actions — are precisely those where the latency cost of providing those guarantees is hardest to absorb. If authentication is designed as a pre-action gate, it will be skipped in the conditions where the stakes are highest.

The correct response is not faster signatures, though that helps. It is pre-authorising at deployment: embedding post-quantum-attested response policies in the system before it operates, so that no per-action authentication is required at execution time. The signature covers the policy, not the individual act.

The hardware crossing

The compute substrate determines what accountability is physically possible. A hardware root of trust that can evaluate an authenticated policy tree in microseconds — without a network round-trip — changes the accountability architecture compared to one that requires a software stack and cloud-side validation.

Hardware attestation, in this framing, is not only about proving identity. It is about the velocity at which accountability can be exercised. A physical agent with a secure enclave that evaluates pre-authorised behavioural policies at hardware speed is a fundamentally different accountability object than one that depends on an external authority at decision time. The hardware design is the authority architecture. For physical AI, those two things are the same thing.

The physical-world care crossing

In care environments, the velocity authority problem takes a less dramatic but more ethically loaded form. A care robot responding to a fall does not have time to confirm consent preferences or escalate to a next-of-kin before beginning a physical assist. The response must begin.

This is not a failure of consent design; it is an inherent property of care in real time. Care robots operating in high-velocity response scenarios need pre-authorised response trees: standing authorisation, granted at enrolment, that covers the physical actions the agent may need to take without per-event confirmation. The accountability question is not whether confirmation occurred at execution time. It is whether the standing authorisation was well-designed, clearly explained, and subject to meaningful periodic review.

Where accountability lives

The velocity authority problem does not eliminate accountability. It relocates it. In physical autonomous systems, the accountable act is not the individual physical decision — the obstacle avoidance, the care assist, the course correction. The accountable act is the design and authorisation of the policy that governed those decisions, executed before the first deployment.

This shift has practical consequences. It demands more rigorous treatment of policy authorisation at deployment time: who signed off, what scenarios were anticipated, what the limits of the pre-authorised envelope are, and what triggers re-authorisation. It means the engineer who designed the response policy and the operator who accepted it are accountable for every action that policy produces — not in hindsight, but by design.

At Asaptic Labs, we treat the velocity authority problem as a first-order constraint in physical AI accountability architecture. When the system cannot ask permission, accountability lives in the policy that governs what it does without permission. That policy must be authored, attested, and auditable — and the principals who authorised it must have understood what they were authorising before the hardware left the bench.