# Evolution 81 — Rollback Plan

## Scope

Development only. Nothing in Evolution 81 touches production, so rollback is local by construction.

## Code rollback

1. `git checkout evolution-80` (or the pre-E81 commit `cab2fa162`).
2. The E81 package lives entirely under `cain/cain2027/e81/`, `scripts/evolution81/`,
   `tests/test_e81_*.py`, `docs/evolution-81/`, `artifacts/e81/`. Removing them restores the E80
   tree byte-for-byte; no shared module was edited destructively.
3. No database migration applies to an existing E80/E79 artifact.

## Data rollback

- New SQLite databases (`mission.db`, `memory.db`, `endurance.db`) are isolated under
  `artifacts/e81/work/`. Delete the directory to discard them; evidence bundles are separate and
  immutable.
- The encrypted memory keyring is 0600 and local; losing it makes old rows unreadable by design.

## Verification after rollback

1. Run `pytest tests/test_cain2027_e80.py -q` → expect 30 passed.
2. Run the E80 offline verifier against `artifacts/e80/bundle` → expect ok.
3. Run the E81 verifier against `artifacts/e81/bundle` only if the E81 artifacts are retained.

## Production rollback (not exercised, not authorized)

If E81 were ever deployed, the procedure would be: drain admissions, suspend new missions via the
kill switch, let leases expire, export evidence, revert the container image to the previous tag,
restore the previous database snapshot, and verify with the previous release's offline verifier.
This procedure has **not** been rehearsed against production and G37 is PARTIAL.
