Tiermark sample audit package manifest ====================================== SAMPLE. Fictional companies. Example Aerospace Inc and its suppliers (EXAMPLE MACHINING LLC, UEI ZZXAMPLE0001, and the others in the ledger) are fictional accounts on Tiermark's test environment. Nothing in this sample is a real company, a real registration or a real attestation. What this is ------------ sample-audit-package-manifest.json is the manifest.json from a real audit package, exactly as the software built it on 2026-10-25 (package id a1137f88-cf4b-49aa-9afb-552e283eaf80), downloaded from the Audit screen of the fictional prime's console. An audit package is one zip for a contracting officer; the help article "Audit packages" (https://tiermark.io/help/audit-packages) describes it. The zip held six files: manifest.json this file: every other file with its size and sha256, and one hash over that list (manifestHash) README.txt what the package is and how to check it ledger.csv every request the prime has sent (8 rows, 8 fictional suppliers) risks.csv the prime's risk register (3 rows) attestations/ZZXAMPLE0001/706b8fae-cb26-4a9d-9ddf-a2cb10d1e87e-v1.json attestations/ZZXAMPLE0001/706b8fae-cb26-4a9d-9ddf-a2cb10d1e87e-v1.pdf one signed attestation, as data and as a document Only the manifest is published here. The other five files are not, so the sample stays small and names nobody; their sizes and hashes are in the manifest. The person who built the package is named by Tiermark user id only. How a package is checked ------------------------ These are the three steps the package's own README.txt gives. They need a shell with sha256sum or openssl, and jq for the third. Every step was run on this package on 2026-10-25; the output is recorded under each one. 1. Every file: sha256 it and compare with its entry in manifest.json. sha256sum ledger.csv openssl dgst -sha256 ledger.csv # the same digest, with openssl Recorded output (both tools agreed on every file): 9b42484de376230463a2b094e3914c693ca4d131eb850713f95b048a06bea6d9 README.txt dc545249eb72ff836b0b04b28ff81f7aec80b68f025e641185cb02967d7841ba attestations/ZZXAMPLE0001/706b8fae-cb26-4a9d-9ddf-a2cb10d1e87e-v1.json 4592945135922be51dd98bbd7cacd38cf4aead28da563cdfe0e9cba89a80bd30 attestations/ZZXAMPLE0001/706b8fae-cb26-4a9d-9ddf-a2cb10d1e87e-v1.pdf 7f96279aa9c11b196b77937776c7609799a397789a147da49d56865b2ba10552 ledger.csv 47040cfba66ceb4339964260b4a09dd27cc6220caf1acef527636e0c44aec564 risks.csv Each one matches the "sha256" of the same path in manifest.json. 2. The list itself: manifest.json carries "manifestHash", the sha256 of the concatenation, in the order the list is written, of \n\n\n for every file. You can run this step on the sample manifest alone: jq -r '.files[] | "\(.path)\n\(.bytes)\n\(.sha256)"' sample-audit-package-manifest.json | sha256sum jq -r '.files[] | "\(.path)\n\(.bytes)\n\(.sha256)"' sample-audit-package-manifest.json | openssl dgst -sha256 jq -r .manifestHash sample-audit-package-manifest.json Recorded output: c5fa1d980af4bb05751df8116be2ed384c2d3e7da1db8bbb385d519cb739c640 - SHA2-256(stdin)= c5fa1d980af4bb05751df8116be2ed384c2d3e7da1db8bbb385d519cb739c640 c5fa1d980af4bb05751df8116be2ed384c2d3e7da1db8bbb385d519cb739c640 The same value is shown in the Audit screen's "Manifest hash" column, is recorded in Tiermark's own record of the package, and is stored in a manifest file beside the zip, so the list can be checked without trusting this copy of it. manifest.json does not list itself. 3. Each attestation: its JSON carries "content_hash", the sha256 of the signed document in canonical form (the keys of every object in alphabetical order, no spaces). Those bytes were written once, when the supplier signed, and Tiermark refuses to read a signed answer set whose bytes disagree with its hash. jq -cS '{answers, attestationId: .attestation_id, format: "tiermark.signed-answers/1", questionnaireVersionId: .questionnaire_version_id, signedAt: .signed_at, signerName: .signer_name, version}' FILE.json \ | tr -d '\n' | sha256sum Recorded output for the one attestation in this package (attestations/ZZXAMPLE0001/706b8fae-cb26-4a9d-9ddf-a2cb10d1e87e-v1.json): 32b3badd401981eb5b42d95aaa25d5f193bb13ddbe1afca5877fae46a23ef67b - which is that file's content_hash. Questions: help@tiermark.io, answered by a person.