# AI Video Signal V23 — Deployment identity operating plan

1. Apply a registered experiment change only with `aivs_change_manager_v23.py` on an extracted copy of the current V23 base.
2. Run `python assets/aivs_release_manager_v23.py stamp SITE_DIR --label <release-label> --change-manifest <manifest.json>`.
3. Run `python assets/aivs_release_manager_v23.py verify SITE_DIR`. Do not deploy if it fails.
4. Package/deploy the stamped site. Direct Upload drag-and-drop can accept the ZIP; Wrangler Pages deploy accepts a folder.
5. In Conversion Intelligence, enter the private admin/export token and run **Verify online deployment**.
6. V23 verifies the release manifest plus critical online file hashes. If Cloudflare Pages Read is configured, it also looks through recent production deployments and matches the deployment whose deployment-specific URL reports the same release fingerprint.
7. Only then use **Mark deployed** for the experiment. The Worker refuses the association unless that online release explicitly contains the registered change-manifest hash.
8. Keep the release verification JSON together with the experiment ledger and rollback package.

## Cloudflare Pages Read (optional but recommended)
Set server-side `CF_PAGES_READ_TOKEN` with Pages Read permission and `CF_PAGES_PROJECT_NAME`; V23 reuses `CF_ACCOUNT_ID`. The token never appears in browser HTML/JS.

## Safety
Deployment verification does not deploy, rollback, or modify production. It proves identity and records evidence. Existing surgical rollback guardrails remain unchanged.