# Verification report — run-d6c4dc15e9f4d15155fee856

## Result

**Paused / no verdict.** The verifier's own predeclared held-out boundary prediction was falsified
before the planned experiment. Open surprise: `s-81ffc3041e1f07b87928e6f2`. This failure is not
converted into analyst success, independent-cross-check acceptance, or a replacement claim.

## Identity reproduction

From the assigned worktrees:

```sh
git rev-parse HEAD
git rev-parse --show-toplevel
git rev-parse --git-common-dir
git status --short
```

Results: engine HEAD `7741d42fc5e4e761e6449bdaf0e4a61d00036a23`, root
`/tmp/opencode/sots-final-research-engine`, common directory `/home/alex/sots-engine/.git`; RE HEAD
`3bfde5a70d874a723e797a695bbd847fd82c0aa7`, root
`/tmp/opencode/sots-final-research-re`, common directory `/home/alex/sots-re/.git`. Both trees are
dirty as expected from the source-identical campaign snapshot; identity was not inferred from HEAD.

```sh
python3 tools/campaign.py --state-root /home/alex/sots-re validate
python3 tools/campaign.py --state-root /home/alex/sots-re status research-completion-abi
python3 tools/campaign.py --state-root /home/alex/sots-re source-binding \
  research-completion-abi \
  --engine-worktree /tmp/opencode/sots-final-research-engine \
  --re-worktree /tmp/opencode/sots-final-research-re
```

Before the surprise, validation passed, status was `verification` with no open surprises, and the
binding matched the analyst package: engine
`ccd8e02083e8d2e2b3e97976ace2273c8f924dfc02a39e919004eaf3544c50fd`, RE
`6696fd5201e144843617cbf6d78b41b5287ad5dcc9fa1e8aaa861d52b64e72e8`.

```sh
sha256sum dumps/sots.exe /usr/bin/objdump \
  verify/results/research-completion-abi/run-9daf5c3b75547271d5c3b4ed/manifest.json \
  verify/results/research-completion-abi/run-9daf5c3b75547271d5c3b4ed/report.md \
  verify/results/research-completion-abi/run-9daf5c3b75547271d5c3b4ed/capture.py
/usr/bin/objdump --version
```

Results: executable `970b7de729956a53094c7eb98aba4270aee98e2fed5daf0d39e290013c90c841`;
objdump target bytes `1eaaef2e7f57c4c7f69115c495e2466f5a8c8e5f3bc42221d092382f30f9d4cd`,
GNU Binutils 2.38; handoff artifacts respectively
`aaada07613a2d2b10d99c4b0a5ee795501a5eba13250c5d3beece587acd8d4a4`,
`6e74ff0197adc6c97f5924ad3f973d5e8922f1480268d1c96dac3dd89000e38f`, and
`66e230d79a2f9903941ff206656b7c26123adb528cbe807c2e1d3132137a20d1`.
`/usr/bin/objdump` is a symlink whose target bytes were hashed; the manifest's 373,888-byte size is
the dereferenced executable, while `stat` on the link itself reports 24 bytes.

## Failed prediction and challenge

The pre-experiment plan required held-out stop `0x00779913` to include a complete `ret 4` beginning
at `0x00779912`. Independent inspection of the raw authority stream shows bytes `c2 04 00`; the
instruction occupies addresses `0x00779912..0x00779914`. An exclusive stop of `0x00779913` can
therefore expose only `c2`, exactly the truncation class that invalidated earlier archives. The
earliest complete stop is `0x00779915`.

This challenges the verifier instrument boundary, not game semantics. The planned objdump and save
subprocesses were **not run**, so there is no positive-execution claim, no archived-state/RNG result,
and no verifier manifest. Existing analyst captures remain measurements only. Actual runtime states
(existing/miss, spare/full, empty/nonempty, short/long, unwind) remain unexecuted; static branches do
not substitute for them. No original-assisted execution, partial/full compare, independent
replacement, or integrated replay occurred.

## Side effects and exact next action

Only verifier-owned plan/report files and canonical campaign surprise/checkpoint state were written.
No lease was acquired; no lab, VM, Ghidra, game, allocator, RNG, engine source, staging, commit, or
push operation occurred.

**Exact next action:** Astra resolves `s-81ffc3041e1f07b87928e6f2` by deciding whether
`0x00779913` becomes an expected-truncated negative and `0x00779915` the fresh complete held-out
control; then a fresh verifier quantum executes the authorized session-bound reproduction.