Permission to act
A navigation tool can suggest a route. A dispatch system can allocate the route to a vehicle. An autonomous vehicle can then begin driving it. Each step transfers more practical responsibility to software and the people operating it. The useful question is what authority has been granted, who can change it, and what happens when someone needs the system to stop. Autonomy and physical action · The remote dispatch example
Autonomy describes how much sensing, planning and action a machine can perform without a person directing every step. The surrounding arrangement still has people who select the task, supply access, maintain the equipment and accept responsibility. More capable software can handle a wider range of circumstances, but capability alone does not establish a proper right to act. What autonomy describes · Human judgement and operating requirements
Australia is already involved
The stakes are already visible in military procurement. The paper follows Anduril's autonomous equipment and its Lattice coordination software, Palantir's information systems and the communications and launch services supplied by other firms. US contracts cited in the paper include ceilings of US$20 billion for an Anduril enterprise agreement and US$10 billion for a Palantir agreement. A ceiling permits orders up to a maximum. Actual orders determine what has been bought. Anduril’s enterprise contract ceiling · Palantir and connected Army procurement · US Army Anduril contract announcement · US Army Palantir agreement
Australia is participating in these systems. A September 2025 government announcement set out an A$1.7 billion, five-year Ghost Shark contract with Anduril Australia for autonomous undersea vehicles, maintenance and further development. An October 2026 announcement described payloads for carrying supplies, deploying sea mines and releasing aerial vehicles. The published account establishes the announced capability and programme, while operational approvals and all targeting arrangements are not fully disclosed. Australia’s Ghost Shark contract · The announced payloads · Australian Ghost Shark contract announcement · Australian payload announcement
Civilian systems carry a related form of power. The reviewed paper records Palantir contracts connected with Australian Defence, financial intelligence and state intelligence systems. For several Commonwealth contract values, the review could access public mirrors of AusTender notices and retained the official links. Those figures therefore keep that access limitation and their stated contract periods. They describe recorded purchases, rather than a complete account of government use. The procurement review’s access limitation · Defence’s recorded contracts · AUSTRAC’s recorded contracts · State and historical records
Who can change a connected system?
A person can decide which personal assistant to use. They generally have much less choice over the software a public agency uses to handle their information. A credible system needs ways to challenge an error, understand who can see the record and limit reuse. Hosting a machine in Australia can help with particular risks, while authority over its software, administrator access and future updates needs its own account. Public records and supplier authority
Updates are especially consequential when one change can reach many organisations. Microsoft's account of the July 2024 CrowdStrike incident estimated that a faulty security update affected 8.5 million Windows devices. It was an outage caused through a trusted delivery channel. The paper uses that event to show how quickly a common failure can spread. Connecting physical action or weapons to similarly concentrated channels increases the importance of independent controls. The CrowdStrike outage comparison · Microsoft’s account of the CrowdStrike outage
Those controls can be described in everyday terms. One role approves a sensitive change and another carries it out. A staged update lets operators inspect a small deployment before extending it. A local team can isolate an unsafe command, preserve the record and restore a known working version. An independent reviewer can examine what administrators are able to do. Contracts need to cover these behaviours during an outage or emergency as well as ordinary service. Independent operational controls · Requirements during updates and emergencies · Local authority and review · NSA and CISA software-delivery guidance · Autonomy in Weapon Systems directive
The paper treats concentrated update authority as a risk to design for. A claim about a particular person being able to redirect a fleet would require evidence about that person's actual access. Ownership, credentials, communications and operational command have specific meanings. Careful scrutiny follows the authority that the evidence establishes. The paper’s control-risk assessment
The same choices in a personal Aura
The same discipline belongs in a personal Aura. Recording information, retrieving it for a task, training a model and publishing a result are separate choices. An assistant might prepare a document while waiting for permission to send it. A person should be able to correct its account, decline its advice, move usable records and stop a connection. In the wider system, sovereignty grows when those freedoms are supported by dependable equipment, understandable agreements and people who can enforce them. The personal Aura arrangement · Keeping retrieval and model training distinct · Consent after disclosure · The right to leave