Corridor Rollout Trigger Checklist

# Corridor Rollout Trigger Checklist
 
Use this checklist before activating the first non-`US→CA` customer corridor (example: `US→UK`, `CN→US`).
 
## Trigger Definition
 
Start this gate process when all of the following are true:
 
- A live customer/pilot requires a specific non-`US→CA` corridor.
- Product + engineering agree the corridor should be activated (not a speculative build).
- A target go-live window is identified.
 
## Go/No-Go Rule
 
Do not activate a non-`US→CA` corridor unless every `Required` gate below is marked complete with linked evidence.
 
## Required Gates
 
| Gate | Required evidence |
| --- | --- |
| `G1 Corridor Decision Memo` | Memo exists in docs with chosen corridor, alternatives considered, regulatory set mapping, and explicit non-goals. |
| `G2 Rule Applicability Metadata` | Rule definitions used by the rollout have explicit applicability scope (`universal`, `origin`, `destination`, `corridor`) and no implicit corridor assumptions. |
| `G3 Wrong-Corridor Negative Tests` | Contract/integration tests show wrong-origin, wrong-destination, and wrong-corridor rules do not fire. |
| `G4 Positive Corridor Coverage` | At least one positive-path test per targeted regulation type proves in-corridor rules fire as expected. |
| `G5 Data + Fixture Readiness` | Relevant reference data is seeded/loaded for target corridor and golden fixtures pass in CI. |
| `G6 Operational Readiness` | Rollback plan documented; owner on-call for rollout window; alerting/logging confirms corridor + rule scope in emitted evidence. |
 
Current baseline `G1` memo: `docs/operations/p7-e-a4-first-expansion-corridor-decision-memo.md`.
 
## Suggested (Strongly Recommended) Gates
 
| Gate | Suggested evidence |
| --- | --- |
| `S1 Dry Run` | Dry run against customer sample data with review notes and issues resolved. |
| `S2 Risk Signoff` | PM + engineering signoff comment in the rollout PR or decision memo. |
| `S3 Customer Comms` | Customer-facing note prepared (scope, caveats, fallback path). |
 
## Evidence Template
 
Record this block in the rollout PR description or decision memo:
 
```md
## Corridor Rollout Gate Evidence
- Corridor: <origin->destination>
- Target customer/pilot: <name or tenant id>
- G1 memo: <link>
- G2 metadata PR/query evidence: <link>
- G3 negative tests: <link>
- G4 positive tests: <link>
- G5 data/fixtures CI run: <link>
- G6 rollback + on-call plan: <link>
- Decision: GO | NO-GO
- Approvers: <pm>, <eng owner>
```
 
## CN→US Corridor Evidence (First Expansion)
 
- Corridor: CN→US
- Target customer/pilot: TBD (gated on customer trigger)
- G1 memo: `docs/operations/p7-e-a4-first-expansion-corridor-decision-memo.md` (PR #381)
- G2 metadata PR/query evidence: `scope_type` on `rule_definitions` (PR #379)
- G3 negative tests: 20 corridor isolation tests + 3 loader integration tests (PR #379)
- G4 positive tests: 7 CN→US unit tests + 2 integration tests (PR #384)
- G5 data/fixtures CI run: SECT301_CHECK + US_232_CHECK seeded (PR #384)
- G6 rollback + on-call plan: `docs/operations/p7-e-a7-cnus-corridor-activation-runbook.md` (PR #385)
- Runtime wiring: CN→US corridor rules evaluated in detection path (PR #388)
- A11 staging dry-run + signoff: `docs/operations/p7-e-a11-cnus-staging-dry-run-signoff.md` (#391 script/signoff scaffold + #394 execution evidence) — executed 2026-02-23: CA PASS (no corridor evidence), US PASS (SECT301_CHECK + US_232_CHECK fired on all 5 CN-origin SKUs)
- Decision: CONDITIONAL GO — G1-G6 complete, A11 executed; requires RLS fixes + customer trigger before production activation
- Approvers: TBD (product + engineering at activation time)
 
## Ownership
 
- Engineering owner: implements and verifies `G2`-`G6`.
- Product owner: owns `G1`, customer readiness, and go-live decision.
- Final activation requires both owners to approve `GO`.