ab-testinglisted

# Ab Testing ## Scope Boundaries - Use when product, pricing, ranking, recommendation, or policy changes may impact user/business KPIs and causal validation is required. - Use proactively when metric impact is uncertain, stakeholder opinions conflict, or ship/no-ship criteria are not explicit. - Use when canary metrics alone are insufficient to support a decision. - Do not use for deterministic functional verification; use `testing-*`. - Do not use for long-term reliability telemetry design; use `observability-*`. ## Goal Produce causally valid, operationally safe, and decision-ready experiment outcomes. ## Shared Experiment Contract (Canonical) - Use `references/ab-testing-governance-contract.md` as the primary reference for recommended structure. - Optional consistency checks (only if your repository enforces manifest validation): - `python3 scripts/validate_ab_testing_contract.py --manifest <path/to/manifest.json>` - Start from valid templates in `assets/`: - `assets/ab-pln-manifest.valid.json` - `assets/ab-dec-manifest.valid.json` - Use decision-rule details in: - `references/decision-threshold-playbook.md` - Do not define local ID formats, lifecycle states, or gate rules in this file. ## Implementation Templates - Experiment charter template: - `assets/ab-experiment-charter-template.md` - Decision record template: - `assets/ab-decision-record-template.md` ## Inputs - Proposed change and explicit decision to be made (`ship`, `iterate`, `rollback`, `hold`)