Named, Confidential
The Department of Defence’s announcement of 19 December 2025 of a multi-year Deed of Standing Offer with Google Australia Pty Ltd for air-gapped hyperscale cloud capability, read beside the public record around it. The record names the entity and does not publish how the capability is operated: the release names no operator and states no value, location or security classification, and Defence says all specific details remain strictly confidential. Whether 18 U.S.C. § 2713 reaches data held in the capability is a legal question the assessment states and does not answer; it sets out what would establish the facts bearing on it.
65 pinned artefacts, 3 inherited under convention 7, 62 first pinned here from a blob another case holds · version 1.0, published 3 October 2026
What the Screening Does Not Ask
A submission to the consultation Getting it right: Building AI infrastructure that works for Australia, lodged with the Department of the Prime Minister and Cabinet on 1 October 2026. The paper premises sovereign AI capability on onshore infrastructure and proposes to leverage existing frameworks rather than duplicate them. On the instruments this practice has read, none of those this submission examines, foreign investment screening, the SOCI Act and the Hosting Certification Framework, asks whether an onshore operator, tenant or frontier developer can be compelled under foreign law. It answers four of the consultation’s six questions, says which it does not answer and why, and puts one question to the department.
15 pinned artefacts, 15 the case’s own · version 1.0, published 1 October 2026
Invoiced, Not Supplied
The Commonwealth’s contract notice register, AusTender, read for what it makes visible about who supplies the Commonwealth and what it does not. A contract notice names the entity the agency contracted with and invoiced and carries no field for whose product was procured; the register’s own guidance says subcontracting arrangements are not reportable, so a count of notices by supplier reaches a vendor’s own contracts and no others. Twelve months of the register were read through an instrument this practice built, froze before any sentence and publishes in full: of 634 ICT notices naming a brand, 478 worth $1,465,918,440 at award were invoiced by a supplier that is not that vendor; Microsoft is the supplier of record on 32 notices and named on 177 under other suppliers; ten vendors named on three or more notices never invoice. Everything is a floor of a floor, and the document says so at full width.
45 pinned artefacts, 25 the case’s own, 16 inherited under convention 7, 4 published assessments of this practice · version 1.1, published 23 September 2026; 2 versions, each at its own hash
Ownership, Not Reach
Four publications of the Australian Signals Directorate on artificial intelligence, read whole from eight pinned captures. All four reach supply: Opportunities for AI in cyber defence asks vendors for model provenance and lineage, a software and AI bill of materials, and the jurisdictions that process or store customer data; Frontier AI cyber threat considerations for boards of directors asks boards about their vendors’ foreign ownership, control or influence; Agentic AI Harnesses requires a trusted model be selected and its provenance assessed; Careful adoption of agentic AI services requires third-party components originate from trusted sources. None of the four asks who can lawfully require production of a model, its weights, its logs, or the data it processes; the words compel and lawful occur zero times across all four, and the compellability detector graded every one NO_MATCH at phrase set 1.0.1 unmodified. In three of the four the supply question sits in a register other than the one that tells the reader what to do, and in Frontier AI boards the terms foreign, ownership and influence occur zero times after line 123 where its action registers begin. Not a finding that any omission was deliberate, and not a claim that the four form a pattern.
9 pinned artefacts, 5 the case’s own, 4 extracted from pins · version 1.0, published 13 September 2026
Sovereign, Undefined
The Australian Government’s own uses of the word sovereign for its Top Secret Cloud arrangement with Amazon Web Services, read against the Government’s own record of that arrangement. The Government used the word three times on the record held, on 4 July 2024 and 14 June 2025, and defined it in none; the four announcement pages name no law, no contracting party and no legal entity, and the spoken record names the partner as Amazon Web Services Australia and no legal entity; the ASD Director-General’s answer that the centres will run under Australian law is quoted and not adopted; AusTender holds 134 published notices under the Australian company’s ABN, 45 to intelligence-community or Defence agencies, none naming the Top Secret Cloud; the United States company is the printed supplier on 50 notices to the same agencies and is among the rows ASIC’s register returned to neither a name search nor a search on its ABN. Version 1.1 corrects two sentences of version 1.0 and retitles it; version 1.0 stands at its own hash. Not a finding that the cloud is, or is not, sovereign in any sense, or of which entity holds the arrangement.
77 pinned artefacts, 18 the case’s own, 59 inherited under convention 7 · version 1.1, published 11 September 2026; 2 versions, each at its own hash
Incorporated, Not Retired
What the Protective Security Policy Framework says it does with a Protective Security Direction, read against what its own record shows it did with Direction 001-2024. The Guidelines say a Direction is incorporated into the next release as mandatory requirements and then retired; Release 2026 says this one is integrated into Requirement 0046; that requirement reads the same and is dated the same in three releases, eight months before the Direction’s own deadline, and the framework’s 2024 list traces it to no Direction. The Guidelines applied the word retired to the TikTok Direction in terms and to this one never, in any edition. Not a finding that any entity is, or is not, bound today.
19 pinned artefacts, every one inherited under convention 7 · version 1.1, published 18 October 2026; 2 versions, each at its own hash
Where the Record Stops
Who can lawfully compel Amazon Web Services Australia Pty Ltd to produce data it holds for an Australian government customer, read from the provider’s own terms, the company registers, the CLOUD Act and the two Australian Acts that decide whom a warrant or authorisation reaches. Every Australian instrument read reaches a person only as a carrier or a carriage service provider; the provider holds no carrier licence on the register as captured; whether it is a carriage service provider turns on the network unit over which its services are supplied, and no published document this practice holds says what that is. Not a finding that the provider is, or is not, inside any definition: the record stops at the network unit, and the assessment stops with it.
21 pinned artefacts, 3 the case’s own, 18 relied on from other registers of the corpus · version 1.1, published 9 September 2026; 2 versions, each at its own hash
What the Change Log Covers
The Information security manual’s change log, read across nine consecutive pairs of releases from June 2024 to September 2026 through the procurement and outsourcing chapter. For the three pairs whose log is held, every control change in the chapter is cited, the June seven under “Minor grammar corrections”; no narrative change is recorded in any of the three logs, 2, 24 and 33 differing lines against no entry; nothing on the record held states what the log covers. Not a finding that any change was concealed, nor that narrative changes should be logged: in the population read, they are not, and nothing states whether they are meant to be.
27 pinned artefacts, 3 the case’s own, 21 inherited under convention 7, 3 extracted from pins · version 1.0, published 4 September 2026
Who the Record Names
The Commonwealth’s five-year Microsoft arrangement names two suppliers, one incorporated outside Australia, publishes no document and assigns no product or service to either. The offshore supplier holds an ABN as an Other Incorporated Entity with no ASIC registration line; Microsoft’s published Australian customer terms name it as Microsoft under Irish law; the hosting certification entry is a product name that matches no entity name on either register. Not a finding on which company contracts for Azure: no retrieved artefact says.
42 pinned artefacts, 38 the case’s own, 2 inherited under convention 7, 2 published assessments of this practice · version 1.0, published 4 September 2026
What the Consultation Publishes
One Home Affairs consultation package links three consultation papers. Two contain the document being consulted on. The third directs the reader to email for a copy of the Hosting Certification Framework 2 Policy, from the address that receives submissions. The Deed of Certification is named as a later phase, and no artefact retrieved describes a consultation on it.
25 pinned artefacts, 20 the case’s own, 5 inherited under convention 7 · version 1.0, published 28 August 2026
What the Certification Is Over
The Hosting Certification Framework’s register divides its Certified Strategic entries into three certification objects: Facility, Enclave and Service. The Deed of Certification defines Service and grants certification over it. The framework’s For Service Providers page defines an enclave in its eligibility criteria. Facility is defined in neither, and in nothing else published.
27 pinned artefacts, 9 the case’s own, 18 inherited under convention 7 · version 1.0, published 27 August 2026
What the Record Can Show
At the Hosting Certification Framework’s Certified Strategic tier, every step the published instruments state is addressed to the provider or to a recipient inside government. Of eleven instruments read, none requires a decision under that mechanism to be published without being asked for. The claim is not that anything is secret - the outcomes are to be asked for.
25 pinned artefacts, 12 the case’s own, 12 inherited under convention 7, 1 first pinned here from a blob another case holds · version 1.0, published 26 August 2026
What the Disclosure Regime Records
Neither Australian instrument that creates a record of government AI use asks an agency to name the model it uses, or whose. Of 111 published transparency statements read, 41 name a vendor or a product and none names a model version.
122 pinned artefacts, 119 the case’s own, 3 inherited under convention 7 · version 1.2, published 2 September 2026; 3 versions, each at its own hash
What the Instruments Require
Of eight published Australian assurance instruments, none specifies a method for assessing whether a foreign government may reach a provider’s data by law, and at least one, the Commonwealth Procurement Rules, does not name that reach at all. Among the eight, the single mandatory requirement asks where things are.
25 pinned artefacts, 16 the case’s own, 9 inherited under convention 7 · version 1.6, published 12 October 2026; 7 versions, each at its own hash
Stated, Not Required
The Information security manual’s procurement chapter states that foreign-owned suppliers operating in Australia may be subject to a foreign government’s lawful access to data belonging to their customers. No control in that chapter requires an organisation to establish whether any particular supplier is. The same chapter names a performer, a standard and a cadence for the IRAP and ASD assessments of managed and cloud services, and none of the three for the supply chain risk assessment it does require.
14 pinned artefacts, 13 the case’s own, 1 extracted from pins · version 1.2, published 5 September 2026; 3 versions, each at its own hash
The Instruments That Exist
The Australian Government published three memoranda of understanding with two United States incorporated companies - two on AI collaboration, one on digital resilience. Each records intentions. Each disclaims binding force, in three different formulations. The only law any of them names is Australian law, and none addresses what happens when the jurisdiction a company is incorporated in directs otherwise.
6 pinned artefacts, 6 the case’s own · 13 claims numbered in the assessment’s scope as at 16 August 2026, 3 with a stated falsifier · version 1.1, published 15 August 2026; 2 versions, each at its own hash
The Question Not in the Set
A published guidance document offers organisations two sets of questions to put to AI vendors. One group is headed “Data protection and sovereignty”, and its explanatory line directs the reader to customer data sovereignty obligations. The three questions under it ask how data is handled, what is retained, and which jurisdictions process or store it. None asks which state can require the vendor to produce it, and neither appendix puts that question in any form.
2 pinned artefacts, 2 the case’s own · 8 claims numbered in the assessment’s scope as at 17 October 2026, 5 with a stated falsifier · version 1.1, published 15 August 2026; 2 versions, each at its own hash
The Unasked Jurisdiction Question
A published report recommends that submarine cable operators be required to locate a network operations centre in Australia, and states this would subject cable operations to Australian requirements “rather than those of another country”. Eighteen printed pages later it records that the same instrument, imposed by the United States, “would potentially give the US Government greater access to the systems”. What a requirement of that kind does when it is imposed on an operator subject to another state’s law is not established in any section where the question would sit.
2 pinned artefacts, 2 the case’s own · 11 claims numbered in the assessment’s scope as at 15 August 2026, 6 with a stated falsifier · version 1.0, published 15 August 2026
The Hosting Certification Exemption
What the critical infrastructure regime asks about a supplier's exposure to foreign law, of which asset classes, and what section 30AB(4) of the Security of Critical Infrastructure Act 2018 removes from an asset connected to a certified service. Version 1.2 withdraws four sentences that were false when written and rewrites two recommendations; no finding moves, and versions 1.0 and 1.1 stand at their own hashes.
15 pinned artefacts, 12 the case’s own, 3 inherited under convention 7 · 43 claims numbered in the assessment’s scope as at 17 September 2026, 15 with a stated falsifier · version 1.2, published 17 September 2026; 3 versions, each at its own hash
Jurisdiction of Control in the Hosting Certification Framework, Strategic Tier
Which legal entity holds each certification at the Hosting Certification Framework's Strategic tier, and which jurisdiction controls it, resolved on primary ownership records for all 28 certified providers.
Jurisdictional Exposure of Commonwealth Bank Cloud and Model Dependencies
A jurisdictional exposure assessment of the Commonwealth Bank of Australia's dependence on United States incorporated cloud and AI-model providers, across two exposures: compellability of data and availability of models.
The Compellability Gap in Commonwealth Cloud Assurance
An assessment of two Commonwealth instruments - the FOCI guidance and the Hosting Certification Framework - and whether either tests if a certified provider can be lawfully compelled by a foreign government.
Broadcom Structural Exposure Assessment
A jurisdictional assessment of Commonwealth dependence on VMware products contracted through corporate entities controlled by Broadcom Inc.
The Jurisdiction Gap
How existing regulatory frameworks leave Australian institutional data exposed to foreign legal reach, and what would close the gap. A submission to the Senate inquiry into artificial intelligence and data centres.
Telstra CLOUD Act Assessment
A jurisdictional exposure assessment of an Australian critical telecommunications carrier under the Security of Critical Infrastructure Act 2018.