The Compellability Gap in Commonwealth Cloud Assurance

Verification status

The assessment is structured in layered attestation. The counts below show what is in the document; the CLAIM verdicts below show the engine result for the verified layer.

CLAIMs are facts tested by the AustraliaOS verification engine against primary sources. ANALYSIS blocks are labelled AUTHOR REASONED: each is the director's reasoning over CLAIMs and names the step at which a reasonable reader could disagree. This assessment carries no RECOMMENDATION blocks: it ends at its Bounds section and proposes no actions.

CLAIM verdicts

Board reflects the verification run of 6 July 2026 at agentos commit 59e80dd.

SUPPORTED indicates the CLAIM is confirmed by at least one primary source. PARTIALLY SUPPORTED would indicate the source pool confirms the substance of the CLAIM but a specific element in the evidence assembly diverges or could not be fully verified against the available source text. NOT SUPPORTED would indicate the source contradicts the CLAIM. UNVERIFIED would indicate the source was inaccessible to verification at the time of publication. The 14 SUPPORTED, 0 PARTIALLY SUPPORTED, 0 NOT SUPPORTED, 0 UNVERIFIED census confirms every CLAIM in the assessment against a primary source the reader can open.

Pinned sources

Version 1.4 rests on 22 pinned artefacts, each listed with its reference, its description as registered and its SHA-256. Fifteen were retrieved on 5 September 2026 and are held with the case. Seven are inherited under the practice’s convention 7 from the companion cases that first retrieved them, compellability-landscape-2026-08 and assurance-method-gap-2026-08; each was re-verified against its recorded hash on 5 September 2026 and the blob is held in that case. Every quotation of a source in the document was tested against the pinned copy and found. The viewing dates printed in the document’s References are those of the first reading, 6 July 2026; the hashes below are of the copies read for v1.4.

Versions 1.0 to 1.3 rested on fifteen addresses with viewing dates and no hashes. A reader of those versions can open every source and check every claim against it, and cannot confirm that what the source serves today is byte-identical to what the assessment read. From v1.4 each row above carries the hash of the copy this practice read, and what a reader can do with it differs by row, measured on 6 September 2026 by fetching each of the fifteen own rows twice. For eleven rows, S1, S2, S6 to S11 and S13 to S15, a fetch of the address returned the pinned bytes, so the hash could be confirmed by fetching on that day; that holds until the publisher changes the page. For S5, the ABN Lookup record, the address now serves different bytes from the pin. For three rows, S3, S4 and S12, the AWS Australia FAQs, the AWS security blog tag page and the Google HCF page, the served body hashes differently on every fetch, so their hashes cannot be confirmed by fetching at all and stand only against the copies this practice holds, which it does not publish. The seven inherited rows were not measured. A hash on this page is a record of what was read; for three rows it is not a check a reader can repeat.

How to trust this record

The integrity of this verification record rests on public-source reviewability. Every factual claim in the assessment is tied to a named primary source, listed above, that is publicly accessible. Any reader, official, or independent reviewer can fetch the same source, locate the same passage, and confirm or contest the verdict for themselves. The verification does not ask the reader to trust an internal record; it asks the reader to check the public source directly.

AustraliaOS operates under a publicly disclosed interim audit-chain state pending migration to Australian-hosted infrastructure. The audit log entries written by the verification engine for this assessment are unsigned, via the JSONL fallback path, and are not yet cryptographically chained under a HMAC key. This is the same interim state disclosed for production on the AustraliaOS landing page. It is named explicitly here rather than left implicit, in keeping with the doctrine of disclosed accuracy the assessment itself argues for. The integrity guarantee on which this record stands is reviewability of public sources by the reader, not the internal audit chain; the chain is documentary, the public sources are evidentiary.

How this record is verified

The assessment PDF. SHA-256: d964c1ad31d43a788bd579430bd72483f5662ec895063eda45bc241a8dce4b5d. Download the file and run shasum -a 256 over it. If the value differs, the file is not the one struck here.

Verification chain: hash, from v1.4. Versions 1.0 to 1.3 predate the practice’s hash-pinning convention: their register records, for every source, a reference, a name, a URL and the date it was viewed, not a SHA-256 and not an archived copy. From v1.4 the register is a manifest of 22 rows, each with a SHA-256, pinned in the case’s attestation record beside the hash of the built PDF, and the freeze gate that releases a build checks that the register it was built against is the register still tracked. The PDF is built deterministically: three consecutive builds of the v1.4 source produced byte-identical files, and the gate rebuilds the document from the committed source and compares it with the committed, served and attested hashes before anything is published.

The timestamp. The timestamp. The receipt AOS-CMP-2026-001-v1.4.pdf.ots is an OpenTimestamps proof over exactly the bytes struck above, submitted to four calendars on 6 September 2026, after the freeze gate passed, and pending confirmation in the Bitcoin blockchain at the time of publication. It establishes that the file existed no later than the moment it was stamped. It establishes nothing about whether the file is correct. Receipt SHA-256: a99c768aff7ebdd98e0780acbd8916b77081cb818b9b2886c6d8fdbfa4f44965. The same bytes are served at the current-file address AOS-CMP-2026-001.pdf.ots. Each earlier version’s receipt is named on its row below.

What this page is not

This verification record confirms that the factual claims in the assessment match what the named primary sources state at the time of publication. The assessment examines the design of two Commonwealth instruments and one program; it does not assess the conduct of any provider or any government entity, and it alleges no wrongdoing by either. It makes no allegation against Amazon Web Services, Google, or any provider named: that a provider holds Strategic certification, and that a United States company is reachable under United States law, are ordinary and lawful facts.

It makes no claim that any particular Australian Government dataset or system is held with any particular provider, at any tier, or in any location. It does not allege that the CLOUD Act has been invoked, or that any Australian Government data has been compelled, disclosed, or accessed. The subject is legal reachability, a standing property of jurisdiction, not any event. The assessment itself, not this verification page, is the decision-support artefact.

Every version, with hash

Every document this page has ever struck now has an address. That convention was adopted 12 August 2026 and applies corpus-wide.

A row marked see Corrections is affected by the correction recorded in the next section.

v1.1's service is established by a third-party capture (Internet Archive, 8 August 2026), not by this practice's own record.

v1.0 was struck by this page on 6 July 2026 and superseded four hours and five minutes later. No capture sampled that window, and the site publishes from a working tree rather than a branch, so the repository cannot answer whether any reader was served it. It is published at its own address for the first time at v1.2.

What changed, and why

v1.4, 6 September 2026 - one sentence of the v1.2 version note withdrawn, one clause narrowed, one sentence named, two facts added, and the sources pinned. The v1.2 version note said “Nothing in the earlier versions was inaccurate. Every absolute in that text is scoped to the instruments it names, and each remains true.” That sentence is withdrawn: two absolutes in the earlier text are not scoped to the instruments they name. Section 3’s clause that nothing requires an entity to reach past the guidance for a method that asks more ranged over Commonwealth requirements and rested on two instruments; v1.4 narrows it on its face to the Direction and the guidance, checked against both pinned texts. Section 6’s close on “the instruments that define sovereignty in Commonwealth cloud assurance” ranges over a class and rests on the three instruments the assessment reads; it is left as written and named in the version note as a rhetorical close wider than the reading. Section 3 also records that the Direction now operates under PSPF Release 2026, dated July 2026, which is organised as numbered requirements, among them Requirement 46 on foreign ownership, control or influence under RISK 06 Third Party Risk Management, and which carries a recommended-approach section headed Monitor and Review FOCI Risks; that no document held maps the Direction’s policy references to that numbering; and that the Framework’s pages carry a reform notice. Every source was retrieved again on 5 September 2026 and pinned by SHA-256, listed above. No finding moves. The withdrawn sentence was found by this practice on 5 September 2026, in a sweep of every universal in its first editions, before any external party raised it; the full account and its reach are in the practice’s corrections register.

This page said, from 6 September 2026 at 03:20 UTC until this regeneration, that from v1.4 a reader could confirm for every row that what the source serves today is byte-identical to what the assessment read. That was false for three rows, S3, S4 and S12, whose served bodies carry a per-request value and hash differently on every fetch, and it overstated the rest, which hold only until the publisher changes the page. The sentence was written the day before the property was measured across the corpus. The Sources section now says, row by row, what a reader can and cannot repeat. Recorded in the practice’s corrections register.

This page’s own hero printed v1.2 in its reference and version cards while its reference strip printed v1.3, from 24 August 2026 until this regeneration. The v1.3 publication moved the strip and the version history and left the two cards, and the correction of 26 August 2026 to the Download block below did not read the hero. The date card printed the first reading’s date without saying so. All three now read from the current version, and the assessed card names both readings. Recorded in the practice’s corrections register.

v1.3, 24 August 2026 - one statement corrected. v1.2 said the Strategic tier’s operative terms sit in a Deed of Certification that is not public. The standard form of that Deed is published - a 20-page Deed of Certification (Template) on the Hosting Certification Framework’s own website, linked from no page on it, published since November 2021 and held by the Internet Archive since 7 March 2022. The statement was wrong when written, not overtaken. What remains not public is what any named provider executed, any variation to the standard form, and any condition imposed under its clause 13.2. This assessment’s boundary rests on those and is unchanged. No finding moves and nothing else in v1.2 is withdrawn or qualified.

v1.2, 12 August 2026 - an addition, not a correction. Section 6 gains a subsection recording section 30AB(4) of the Security of Critical Infrastructure Act 2018 and the critical infrastructure risk management regime; Section 7 gains its limits. Nothing in the earlier versions is withdrawn, corrected or qualified, and no finding moves.

A correction to this page's own version history. A revision published at 13:29 AEST on 12 August 2026 was mislabelled v1.1; it is v1.2. In that window this page carried a row stating "v1.0 · fd31859858a2ad1e…", which was false - those are v1.1's bytes. The false state was captured by the Internet Archive at 03:31:54 UTC on 12 August 2026 and remains retrievable there; this practice cannot withdraw that capture. The full account is in the Corrections section of the v1.2 document.

Assessment PDF

The full assessment, authored and signed by the director, is available below. The verification status set out on this page is reflected in the document footer.