I read this as a read-only F3 release-gate revalidation - I’ll trace the frozen candidate’s evidence, implementation, authorization and replay artifacts, then return a strict PASS/FAIL with residual risk and checkability.


The relevant scope is isolated to Task 27’s supplemental cleanup chain and the pre-existing F3 record; I’m now cross-checking those records against the controller’s actual transaction/replay semantics and the frozen v38 archive.


I read this as a read-only F3 release-gate revalidation - I traced the candidate, cleanup authorization, transaction semantics, terminal state, and frozen artifacts without mutation.

## Verdict: PASS

**F3 may be checked: YES.** Supplemental cleanup did not alter or weaken shipped candidate `d1109d8f...39112`.

### Exact evidence

- Existing F3 receipt: `task27-v38-final-verification-f3.json`
  - SHA-256 `55bdbc3f0f2ada90c94dc87dde365b4f19b3c868a839d700575835b498ab7740`
  - Status `PASS`; all 13 reliability/exactly-once requirements pass.
- Frozen candidate remains bound to:
  - Candidate `d1109d8f78aaccf949ec4f664d9e62584c3cca33032030518bc3e2d712239112`
  - Hermes wheel `f8b3c779...c1860b1`
  - Delivered seal `54be54cf...752f67`
  - Postfreeze seal `3002d815...5878f6`
  - Direct scan found no writable entries or symlinks in the delivered root.
- Supplemental controller:
  - SHA-256 `65fc6c93e4ba7b0efaff84563f50d37875d150551a00260e7f3ade7b9d009e9f`
  - Tests SHA-256 `3833be95b478bcce4e96c6f7b95c07930d86e8b3f804fd7a5fffc324416fa3c1`
  - Matrix expands to 22 cases and supplied execution is 22 PASS.
- Authorization chain:
  - Preview SHA `670c9d07198942503a9da892d4dc723312ec60ccab538c8552f78a1b22660287`
  - Approved preview seal `7d7b9d5b...61889`
  - Final authorization SHA `83a46c25d8a0ef67c71511e0b1786154f075a2b4572f9b4f9feaec34a6d3e6f1`
  - Execute permission seal `6cd72f0c...26774`
  - Controller, candidate, wheel, preview, identity, paths, stopped-service constraint and prior cleanup receipt are all pinned.
- Deterministic operation recomputes exactly as:
  - `sha256("task27-supplemental-cleanup-controller-v1:<permission-seal>")[:32]`
  - Result `005a3c3f9897e2d298a9a7409759509e`
- Consumption record:
  - `authorization-consumed.json` SHA `8e6b7d0bb30fc891d20b6fdf9a02edaf879546dce8c8328598ab98e9fb689d75`
  - Status `CONSUMED_ON_COMMIT`, bound to the operation, authorization and receipt path.
- Terminal receipt:
  - SHA-256 `13b28b5745cf1fb6e8aa9457f14ad86dbf972c3c203394e2fd919d99b7bf659d`
  - Byte-identical to frozen archive `receipt.json`.
- Frozen recovery archive:
  - Manifest SHA `636acca796ef627cc488c85d5cbc79894eaaa1ee68bbd8660aaf7692d4b9b7e2`
  - Source/copy digests match:
    - Outbox `29f118ab...bd104`
    - Membership `ff57a22a...e367`
  - Directories `0500`, files `0400`, zero writable entries, zero symlinks.
- Terminal live state:
  - Outbox absent.
  - Membership directory absent.
  - Service `inactive/dead`, `MainPID=0`.
- Replay/idempotency:
  - Existing fixed output is checked before execution and causes `receipt reuse refused`.
  - The 22-case matrix covers one-use refusal, bad seals, authorization mismatch, drift, foreign state, unsafe entries, and exact rollback.
- Rollback/recovery:
  - Faults after archive copy and after pruning restore byte-equivalent source state and remove partial archive state.
  - Committed archive retains byte-recoverable copies.

### Claim boundary

The shipped candidate’s provider-delivery exactly-once claim remains supported: atomic authority claim before provider I/O, one transport, one audited receipt, permanent consumption on success/failure/unknown outcome, and no retry after unknown outcome.

Supplemental cleanup supports one successful committed execution and process-level rollback; this is not a universal distributed or power-loss exactly-once guarantee.

### Residual risk

- `receipt-hashes.sha256` is stale: its check currently fails for `task27_final_cleanup_controller.py` and it does not include supplemental terminal artifacts.
- `task27-supplemental-verification-receipt.json` records the older 20-test/controller revision, not the final 22-test hashes.
- Cleanup rollback is process-local; SIGKILL/power loss between filesystem operations would require manual recovery from the frozen archive.
- Integrity remains owner-permission/hash sealed, not externally signed or WORM against a privileged host administrator.

These are evidence-housekeeping and host-trust limitations, not F3 behavior regressions.