AI VIDEO SIGNAL V42 — FINAL PRODUCTION RUNBOOK

1. DEPLOYMENT
- Upload the V42 ZIP to Cloudflare Pages production.
- Do not edit affiliate destinations during deployment.
- After deploy, open Conversion Intelligence and run V42 Production Health.
- Verify exact release identity before associating any experiment or remediation with production.

2. HEALTH
Critical: release manifest identity, probe hashes, AFFILIATE_EVENTS binding.
Operational: Analytics Engine read, AUDIT_DB D1, Awin programme API, EXPERIMENT_LEDGER KV, Cloudflare Pages read API.
READY_CORE is acceptable when optional integrations are intentionally unconfigured. ACTION_REQUIRED is not.

3. ECONOMICS
- Approved commission is the only realized revenue input.
- Pending commission is not revenue.
- Do not combine currencies into one EPC or revenue total.
- Release attribution is association, not causal proof.

4. CHANGES
V42 is a structural production freeze. Reopen architecture only for a critical defect, broken affiliate tracking/destination, verified SEO integrity failure, mandatory API/provider migration, security/privacy requirement, or real economic evidence supporting one controlled change.

5. ROLLBACK
- Prefer Cloudflare's previous known-good production deployment when a V42 critical regression is verified.
- Otherwise redeploy the archived V41 package whose fingerprint/hash are recorded in rollback-readiness-v42.json.
- Never overwrite unrelated later changes with a broad page restore; preserve the surgical rollback discipline.

6. NORMAL WORK AFTER V42
Focus on qualified traffic, click quality, Awin approvals, validation timing, controlled experiments and remediation evidence. Do not create new structural versions without a trigger listed in production-freeze-v42.json.