# Production follow-up verification

Two closed native Windows captures test published source commit
`7bb366f66a8c6f8b6f66fc9b04c9e3b39f84b78e`:

| Capture | Executed scope | Result |
| --- | --- | --- |
| `production-followup-1` | Core unit tests plus eight named source/omission integration targets | 180 passed, 0 failed, 0 ignored |
| `production-core-2` | Full `oa-core`, including its doctests | 511 passed, 0 failed, 1 ignored |

The ignored test is `inheritance_chain_validation_scaling_probe`, an explicitly
opt-in scaling probe. These runs used Rust/Cargo 1.98.1 and the native Windows
gnullvm toolchain, locked offline dependencies and incremental compilation off.
The focused run inherited Cargo's jobs setting; the full core run set one job.
UTC execution intervals on 2026-09-13 were 11:32:40–11:36:22 and
11:36:51–11:40:23. Complete commands and environment receipts are retained.

Both captures contain the same 613 unchanged input files. Their original
`inputs.json` SHA256 is
`b9a161be8aca264a6dcf4e7df5cbb7a4f9d999411f1da97430ec0eb3a9929566`.
The original source ZIP SHA256 is
`79dfd5167779094f30f0ee7bdcd678935f7471b294fa2193cfcfd4a5a843459c`.
These are executed snapshots, not a new inventory of the current working tree.
Later uncommitted consumer-test changes are not included in this evidence.

`evidence.zip` preserves each gate's six original files: input manifest, source
ZIP, stdout, stderr, start receipt and result receipt. It also preserves the
exact `gate-policy.py` producer. `capture-files.json` inside that archive pins
all 13 original payloads. Outer `files.json` pins every other package file;
the publishing Git commit identifies the outer manifest.

Run the following from this directory with Python 3.10 or newer:

```text
python -B verify.py
```

Verification reads only: it checks exact memberships, duplicate ZIP entries,
hashes, fixed source/helper pins, all archived input bytes, start/result and time
consistency, commands, raw named outcomes and suite totals, compiler receipts,
and identical inputs across both runs. It never extracts files, builds code,
looks for historical binaries on the machine, or recaptures current sources.
The producer has machine-specific paths and needs adaptation for a new run.

No binaries are distributed. The 9 and 49 compiler-artifact entries are
historical receipts, not independently rehashed runnable artifacts in this
package. This verifies core source behavior on native Windows; it does not
establish Linux, graphical workflows, public service/CLI consumers, strict
Clippy, packaging or release acceptance.