Migration assurance
Migration quality gate
The quality gate converts findings into a single, defensible readiness status using fixed rules. It never claims 100 percent migrated; a clean result is scoped to what was tested. The gate is deterministic and versioned, so the same findings always yield the same status.
- Statuses: BLOCKED, AT_RISK, READY_WITHIN_TESTED_SCOPE, NOT_VERIFIED
- Method: Deterministic, versioned gate. No AI.
- Honesty: Never reports 100 percent migrated; scoped to tested coverage.
How the gate decides
Only unresolved blocker findings backed by deterministic direct evidence force BLOCKED. LOW-confidence findings, MANUAL_VERIFICATION findings, comments/docs/test evidence and absence heuristics cannot force BLOCKED; they produce AT_RISK or lower review states. High-severity findings without a qualifying blocker produce AT_RISK. A clean tested scope produces READY_WITHIN_TESTED_SCOPE. Insufficient coverage produces NOT_VERIFIED rather than a false green.
Why deterministic
A versioned, rule-based gate is auditable and reproducible. You can defend the status to a stakeholder because it follows fixed rules, not a model opinion.
Frequently asked questions
Does a READY status guarantee success?
No. It means ready within the tested scope. Static analysis proves the presence of problems, not the absence of every possible one.
Official sources
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/report