ODM Migration Runs: A Full Governance Workflow for Twenty Thousand Rules

A migration of 20,000 ODM rules is not a one-shot operation. The source keeps taking hotfixes while the review is underway. The migration lead needs weeks. The risk reviewer at the end needs numbers, not a handshake. The Migration Runs workspace is built for this shape.

**Two paths, different purposes**: - Direct import: post an export, read the gap report, post again to commit. The right shape for evaluating the importer. AI-assisted gap analysis lives on this path. - Migration runs: the persistent path. A run owns its uploaded source, a review row per source artifact, the scenarios replayed against what shipped, and certificates. This is the right shape for performing a migration.

**The migration run lifecycle**: Upload → AI gap analysis → Per-artifact review → Scenario replay → Certificate → Promote.

The AI gap analysis ('POST /odm/assist') is grounded only in the analyze report for the uploaded export — it does not invent rules the source didn't have. Per-artifact review means a migration lead reviews each converted artifact before it advances. Scenario replay proves behavioral equivalence on the final output — not on the conversion, on what shipped.

**Certificates**: when a run completes, the platform generates a certificate: the source artifact count, the review disposition per artifact (accepted / modified / rejected), the scenario replay results, and the migration lead who approved each step. This is the artifact the risk reviewer reads.

**Keeping pace with production hotfixes**: the source can be re-uploaded mid-review. The run recomputes the gap report against the new upload and surfaces new or changed artifacts for re-review. Rules that were already reviewed and not in the diff are not re-opened. This is how a 12-week migration stays coherent when ODM takes 40 hotfixes in the same window.