# Sovereign Evolution 2 — kit signing input and verification instructions

**The kit is NOT signed.** This session has no access to the production release key and did not use it.
Only the owner (or a signer they authorize) signs.

## What gets signed

The signing input is `EVIDENCE_MANIFEST.json` in this folder, exactly as committed (its bytes, not a re-serialization).
It lists every file in the `sovereign-evolution-02` slot with its sha256.

```
sha256sum reports/sovereign/evolution-02/EVIDENCE_MANIFEST.json      # record this digest before signing
```

-82's kit pipeline signs the whole kit release. The owner signs that release's manifest with the release key, and
the slot manifest above is a member of it.

## How anyone verifies (no CAIN code needed)

1. Check every file against the slot manifest:
   ```
   cd sovereign-evolution-02/
   python3 -c "import json,hashlib;[print('OK ' if hashlib.sha256(open(f['path'],'rb').read()).hexdigest()==f['sha256'] else 'BAD', f['path']) for f in json.load(open('EVIDENCE_MANIFEST.json'))['files'] if f['in_kit']]"
   ```
2. Verify the kit release signature with the owner's published public key, using the kit's own
   verification instructions (auditor kit README / Verification Center).
3. Recompute the source commitments with access to the repository: `git show <commit>:<path> | sha256sum` for
   each entry under `source_commitments`.

Do not treat the slot as signed until step 2 succeeds against a signature the owner produced.
