OWNER HANDOFF — PREPARED, NOT EXECUTED

STOP for separate independent acceptance of this public.2 candidate before owner
signing. No private key access or signature creation is authorized in preparation.
After acceptance the owner may use their independently trusted existing signing
key locally to sign the exact detached MANIFEST.json and RELEASE-BINDING.json.
The external handoff supplies exact digests and verification commands. Signing the
binding as well as the manifest authenticates the exact ZIP digest. Do not regenerate
either manifest or ZIP to make failed verification pass, reuse a public.1 signature,
or insert signatures into the frozen archive. Preserve detached signatures outside.
Original Release 220 signature covers its old manifest and containers, not derived
projection bytes. No separate redaction attestation exists. Signing authenticates
bytes and declared derivation; it does not independently witness historical events.
Publishing, deploying, indexing and website-gate activation require a separate owner
instruction. No publication destination or action is assumed here.
