# Evolution 81 — Takeover Review (2026-11-16)

A later session re-derived the headline numbers from raw rows with
`verification/e81_independent/recompute_headlines.py` (standard library only, imports no CAIN code).
Same project, not a third party. Result: **17/17 checks pass**,
5 findings.

## Findings

| id | severity | finding | effect |
|---|---|---|---|
| F-01 | LOW | Reported call total undercounts the ledger. cost_report/docs say 1156 real local calls; the main ledger holds 1475 (319 early rows carry the older label LOCAL_MODEL_INFERENCE) and the endurance ledger a further 114. Total 1589. | An undercount, not an overclaim. Token totals and inference seconds in the cost report already cover every ledger row, so the cost estimate is unaffected; only the call count is wrong. |
| F-02 | MEDIUM | Gate audit log is forked, and the summary reports chain_ok over a tail only. 1 fork point(s) at seq [1987]: two pipeline processes appended to one file concurrently, each continuing from the tail it read at start-up. Every row hashes correctly and links to an existing row, so this is a concurrency defect, not tampering. gate_audit.json says chain_ok=True but checked only 12 in-process rows of 2094. The gate audit log is also not part of the signed bundle. | Writer fixed (file lock + on-disk tail) in cain/cain2027/e80/core.py with a regression test; the historical file is preserved unmodified and must not be described as an unbroken chain. |
| F-03 | LOW | Benchmark call count reflects only the final resumed process. rows account for 700 calls across 15 arms; the report says 412 (the budget of the process that finished the run after a resume); the ledger holds 855 rows for the mission, including calls from an interrupted first attempt whose arms were re-run. | Accuracy figures are unaffected. Quote 700 calls for the scored rows, not 412. |
| F-04 | MEDIUM | Pre-registration timestamp postdates the first benchmark calls. preregistration.json created_utc=1794828568.809831 but the first M-bench call is at 1794825050.862719 (59 min earlier). The file is rewritten at every process start and the run was resumed, so the original timestamp was overwritten. | The criteria are fixed in code and the hypothesis was REJECTED, so there is no selective-reporting gain, but 'written before the run' cannot be shown from the artifact. Writer fixed to never overwrite. |
| F-05 | MEDIUM | Durable stores and the branch itself existed on one host only. `*.db` is gitignored, so the SQLite mission/endurance stores were never in the repository, and evolution-81 had not been pushed to the development replica when the host lost power (the replica held evolution-80 only). The stores survived on disk; a disk loss would have left only JSON exports of them. | Stores force-added to the branch as evidence and the branch pushed to the replica by the takeover review. Replicate after every milestone commit, not at the end. |

## Gate statuses changed by the review

- **G23 PASS -> PARTIAL.** The drill shows execution on a second host and lost-acknowledgement recovery with no
  duplicate effect. Mission state never left the first host; a mission resumed on another host after its
  coordinator host failed was not shown.
- **G30 PASS -> PARTIAL.** Authenticated retrieval works against a local service. It is not wired into or
  deployed on clawx.click.

## What was confirmed

- Every one of 1475 model calls traces to an ALLOW decision; no EXECUTE without ALLOW.
- Gate audit: 2094 rows, every hash recomputes, every link exists; linear chain = False.
- Benchmark accuracies and the "collaboration not superior" verdict follow from the stored rows.
- Endurance: 3600.0 s of wall clock, calls spread across the hour.
- Durable stores pass SQLite integrity checks after the unplanned host power loss of 2026-11-16 13:43 UTC,
  with no duplicate effect keys. The host stopped logging at 2026-11-16T13:42:59Z and booted at 15:57Z. No E81 mission was running, so this shows durable state surviving a real power loss; it is not a mission resumed mid-flight across a reboot (G07 stays PARTIAL).

## Repository recovery

The power loss truncated the last commit on `evolution-81` (`7bf919cec`) and 20 sibling objects to zero bytes.
The branch was restored to `7884f75b0` from its reflog; the interrupted commit's files were intact in the working
tree and were recommitted. Nothing was rewritten in history.
