# Original Responses API audit provenance verification

Date: 2026-09-04. Result: **PASS for the retained evidence and public derivative**.

No live API request, network call, credential use, publication or change to any historical file was made. Only report artifacts were written in this current workspace.

## Verified results

| Check | Outcome |
|---|---|
| Core source run | RSP1100-CORE-20260819T190014Z, COMPLETE, Protocol 1.10.0 |
| Core source files | 46 files; canonical tree and manifest match published article |
| Optional source run | RSP1111-OPTIONAL-20260819T212207Z, COMPLETE, Protocol 1.11.1 |
| Optional source files | 10 files; canonical tree and manifest match published article |
| Selected results | 42 core + 6 optional = 48 unique model/case keys |
| Every selected evidence file | All 48 SHA-256 hashes, identities, statuses and assertion-failure lists match the public derivative |
| Combined outcome | 34 PASS, 14 FAIL; zero RECOVERED, BLOCKED or selected NOT_RUN |
| Flash / Pro | Each has 24 results: 17 PASS and 7 FAIL |
| Failure categories | 6 media-type errors; 6 missing final Web Search messages; 1 JSON-schema conformance error; 1 punctuation mismatch |
| Usage | 281,681 input; 235,776 cached input; 4,009 output; 44 reasoning; 285,690 total tokens |
| Usage coverage | 40 results report usage; 8 do not. Missing is not zero. |
| Dated peak-rate estimate | $0.246114; not an invoice or measured account debit |
| Current Protocol 1.11.1 frozen package | All 14 frozen file byte hashes match |
| Original combined public package | All 27 covered files and package tree/manifest match |
| Historical source refresh records | All 12 records report HTTP 200 HTML and frozen-byte or required-contract-marker checks |

## Published hash identity

Core manifest: `b297b7e1005c3905b03ee01840145d832568fbc51ee36fa76bdc1139a6ccc4dc`

Core canonical tree: `026b7257085220df7cf48cdf34c4aefaf8e70ad09e8b1b94d0b0f2ebc109a44a`

Optional manifest: `f27b622e7025454476b7f928d55d9a76305667c53d08fc9fe5b0ff7d114f003c`

Optional canonical tree: `7df2bcd2a7fee2178299c921d76523a4c94e67e8e7a193fc36e13b2865367cb4`

Original combined `public-results.json`: `b84a59b5c73c8a62ba7a029e543b5fdf01bb53c24e54e3fe33ab0ec279bbd9d9`

## Reproduction performed

1. Inspected the historical derivative implementation before executing its explicit read-only `--verify` mode. It regenerated the public JSON byte-for-byte and passed the source gates without writing files or making network calls.
2. Independently recomputed source manifest/tree hashes, read each selected evidence record, compared its identity/status/assertion failures to the public result, recounted all outcomes, recalculated public usage/price totals, and verified the current frozen package and original public package checksums.
3. The publisher retained a separate machine-readable verification record; it is not included in this download.

## Boundaries that must remain explicit when publishing

- Hash agreement proves integrity against the retained records, not independent witnessing of the historical live execution or the correctness of every assertion in the original test design.
- The superseded Protocol 1.10.0 fixture, runner and protocol hashes are cross-checked against its immutable run manifest and frozen historical public anchor. Their historical source bytes were not recovered by this review. Current Protocol 1.11.1 bytes must not be mislabeled as the core run's historical source.
- Do not call a downloadable public-results JSON a complete rerunnable raw-evidence archive. It permits inspection and recalculation of sanitized aggregates; raw request/response/credential/account material remains private.
- Original raw run directories and private manifests must not be published automatically merely because their checksums passed. Publication requires the separate safety review.
- The original derivative's `claims_state` and README retain a historical “publication not authorized” workflow marker. This is old preparation-state metadata, not a contradiction of the user's new authorization. Preserve original bytes and explain that historical marker in a new release README instead of silently altering the original evidence file.
- Historical source refresh checks were verified as recorded; no claim is made here that current provider behavior still matches the August 19 observations.
