verify_soak.py.txt is the verifier exactly as it was signed into the claims registry
(sha256 deed0270d115ba2cf509820cc7ec464fa835c76420971921558d4e14ac1e0cb4). It is kept unchanged.

verify_soak.v2.py.txt (2026-09-27) supersedes it. It fixes two verifier bugs: fast-path
commits were not accepted, and a soak that ended before 72 h was not reported as
"STOPPED EARLY". Use v2 to verify the checkpoints:

    python3 verify_soak.v2.py.txt <this directory>

OUTCOME (recorded 2026-09-27): this soak stopped after checkpoint 24 (about 24 h of 72 h).
verify_soak.v2 returns VERDICT: FAIL, because checkpoints 8, 11 and 12 (among others) carry no
MCPGate enforcement evidence: the enforcement probe hit connection errors. Consensus itself stayed
consistent: 0 divergences, 0 anomalies, and every certificate verified. The claims registry entry
C42-SOAK-72H still reads "IN PROGRESS" with status UNVERIFIED. Treat it as FAILED / STOPPED EARLY.
The multi-region soak (soak-multiregion-2026-09-26) is a separate run.