Invoiced, Not Supplied

Verification chain

Four things are pinned, and each can be checked independently of the others.

The assessment PDF. SHA-256: fe4bc9a821824605dcd2a0518a0953d144fea58cbc8dc999bc81f5da562305c6

Download the file and run shasum -a 256 over it. If the value differs, the file is not the one struck here.

The timestamp. The receipt AOS-SFR-2026-001-v1.1.pdf.ots is an OpenTimestamps proof over exactly those bytes, submitted to four calendars on 23 September 2026 and pending confirmation in the Bitcoin blockchain at publication. The receipt served here carries no Bitcoin attestation and is pending still. 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: da5b61e02af9c2b7e123d4cb809155090a7267b8b28add8200fe8d02226091da

The assessed source. The assessment rests on forty-five pinned artefacts in three kinds. Twenty-five are captures this practice retrieved on 16 September 2026 and holds as served: the feed’s own schema and specification, the Open Contracting Data Standard it declares, one contract notice page, the Department of Finance’s data dictionary and Resource Management Guide 423, and twelve pages retrieved as search steps and pinned as such. Sixteen are inherited under convention 7 from general-findings/austender-buyer-sweep-2026-09 and general-findings/commonwealth-procurement-rules-2026-09, each blob re-verified against its origin’s hash and copied here. Four are this practice’s own published assessments, copied by hash so that a rebuild of an origin case cannot move them. Each blob was re-verified against the hash its row records when this page was generated; a miss would have stopped the render. Quotations were checked against the text layer of each pinned artefact, a web page with its markup stripped, the PDF’s extraction, the CSV and JSON as bytes, and the 30 quotations the document’s body makes are listed with their blobs in QUOTATIONS-2026-09-16.tsv; the quotations of version 1.0 in the version note and Corrections are tested against version 1.0’s PDF in RULE-15-AUDIT-V1.1-2026-09-22.md; every count states the artefact it was taken from and the test that produced it, and every statement that something is absent states the population searched. The instrument is published in full at github.com/australiaos/austender-supplier-field-instrument: the brand list, filter terms and shape terms the document cites by hash, the pull and measurement scripts rewritten to read them and nothing else, the request logs and the hash list of the 703 pages; and, from version 1.1, recompute/figures.py and recompute/nobrand.py, which compute every figure at award, with the two tables version 1.1 adds, NO-BRAND-DESCRIPTIONS-v1.1.tsv and AMENDMENTS-P2-2026-09-16.tsv. The scripts reproduce the method, not the pull; the repository’s README says what a reader can and cannot verify from it.

Re-fetch, measured at this case’s own pins. The log at RETRIEVAL-LOG-2026-09-16.tsv records every one of the twenty-five own captures fetched twice within the minute under convention 50: eleven pairs were byte-identical and fourteen hashed differently. For those fourteen the difference, measured against two further fetches about an hour later, lay in per-request tokens the servers issue and the visible text was identical; the second bodies of the original pairs were not kept, so the register’s word for them is unstable and the document’s Limitations say what the word covers. Fourteen of the sixteen inherited rows are unmeasured, because the sweep’s pull made each of its 703 requests once; the two Commonwealth Procurement Rules rows carry their origin’s stability, each fetched twice within the minute on 8 September 2026 with equal hashes. The four published PDFs were not fetched. No row is a Wayback Machine memento.

Of the forty-five artefacts, none is a third-party archival copy: no Wayback Machine memento is pinned here and no independent capture of any row is held. The twenty-five own captures were retrieved from the publishers by this practice; the sixteen inherited rows stand on the registers named above; the four published PDFs are this practice’s own. A reader must rely on this site, on those registers’ pages, or on the publishers’ servers.

The build. The PDF is produced deterministically from tracked source by build.sh, with SOURCE_DATE_EPOCH pinned to midnight UTC of 16 September 2026, version 1.0’s publication day, which does not move at any revision. Repeat builds on one machine and one toolchain are byte-identical; independent third-party reproducibility is not established and is not claimed. Verify by SHA-256, not by rebuild.

Version history

Two versions. Each row records the date the version was made and the date it was published. The current version is v1.1; every earlier version stays published at its own address with its own hash, and what changed is under Corrections below.

The cover carries 23 September 2026, the day this assessment was published. The reading it records was made on 22 September 2026, the date the version table gives as assessed. Two dates are recorded because there are two acts, and the cover carries the later one.

Corrections

What changed in v1.1, and why

Version 1.1 corrects the value method of version 1.0, which was wrong when made. Version 1.0 counted each notice at its latest release, on the premise that an amendment carries the notice’s cumulative value. The register states no such thing, and some amendments contradict it: over the notices measured, 63 of 1,046 amendment releases carry a value under $1. Every value in version 1.1 is the value at award, from the notice’s original contract release. Amendments are listed apart and never added, and every value figure is a floor over the award releases, not a total. One finding moves: the vendors named on three or more notices and never the supplier of record go from nine to ten. One count moves: the notices carrying one company’s ABN under another’s name go from two to one. Most values move. The version note at the head of the document sets out every change, and its Corrections section lists each one. Version 1.0 stays published at its own address with its own hash, and its bytes do not move.

Correction, 21 September 2026, now corrected in v1.1. The assessment states that each notice’s latest release carries its cumulative value. For some amended notices it does not, so the stated value method was wrong when the assessment was made. One finding changes: the vendors named on three or more notices and never the supplier of record become ten, not nine. One count changes: the notices carrying one company’s ABN under another’s name become one, not two. Most values move. The detail is recorded in the practice’s corrections register, and a corrected version will be published by 2 October 2026.

Any correction to this assessment is recorded here and in the practice’s corrections register, and the published bytes of each version do not move.

Corrections made before publication are not listed here. They are recorded in the case’s own pre-insertion audit, which is tracked with the source.

Assessment PDF

AOS-SFR-2026-001-v1.1.pdf · 158,761 bytes · 17 pages

SHA-256: fe4bc9a821824605dcd2a0518a0953d144fea58cbc8dc999bc81f5da562305c6

OpenTimestamps receipt