# Bench entry 2026-10-07: gpt-oss-20b on an Apple M5 Pro (24GB), third pass: the full suite

- FINDINGS.md: the findings, with entry two's values in brackets for the same rows; the header carries the manifest root and the WitnessKit seal head
- PROTOCOL.md, INTAKE.md, LOG.md: what ran, what did not and why, how the product was obtained, the dated log
- protocol-local-model-runtime-v2.md, protocol-adversarial-suite-v1.md, protocol-kits-identitykit-v1.md, protocol-kits-mandatekit-v1.md, protocol-kits-budgetguard-v1.md, protocol-kits-witnesskit-v1.md, protocol-kits-rememberkit-v1.md: the protocols this entry ran under, as they stood on the day; REPORTING.md: the findings format
- harness/run-suite.sh: the session script that sequenced the published harness commands, one server at a time (paths are shown relative to the home directory)
- evidence/: speed JSON, egress and memory samples, the server logs; suite/pass1, pass2, pass3, suite-low, suite-high and suite-32k (one JSON per run with the transcript, the calls and the signed WitnessKit chain, plus summary.md, summary.json and run.log); may/, spends/, who/ and remembers/ (the kit checks written before any server start, and the live variants); did/ (chains verified three ways, the tamper demo, entries by verdict, the seal verification); concurrency, sustained-load and warm-load records; MANIFEST.json and MANIFEST-chain.json (every file hashed and signed), MANIFEST.chain.json and MANIFEST.pubkey.txt (the WitnessKit seal over the folder), config.json
- bench-gpt-oss-20b-2026-10-07.zip: the same evidence as a bundle, the format a contributed run arrives in
- To check the evidence yourself: download the bundle, unzip it, and run `node bench.mjs verify --evidence <folder>` from the harness package (bench/harness in the harness zip published alongside the entries). It re-hashes every file against the signed manifest and re-scores every run from its recorded calls.

Home-directory paths in the logs are shown as ~ and the account name as "user", except in three files written after that rewrite and before signing (config.json, did/manifest-verify.txt and remembers/planted/foreign-key-summary.json), which carry the model file's full path and are published as signed.
