| Generated Mulesoft project |
This is the primary deliverable — without it the system has produced analysis, not migration. Removing it leaves the developer with policy mappings but no runnable artifact. |
| Policy mapping confidence score |
Without this, every generated migration looks equally trustworthy. Removing it collapses the review queue — either everything gets reviewed (negating the automation) or nothing does (negating the safety). |
| Human-review queue with annotations |
Removing this means low-confidence migrations either block the pipeline or silently enter production. The annotation (why flagged) is what makes review tractable — without it, the reviewer must re-derive the reason from scratch. |
| Migration progress tracker |
Without it, there is no operational visibility into a multi-API program. Removing it means no one knows how many APIs are migrated, how many are in review, or where the blockers are. At 30 APIs this is annoying; at 300 it is a program management failure. |
| Corpus feedback loop |
Removing it means the 50th migration is as uncertain as the 5th. The system does not improve. Human review load stays constant instead of declining. The only mechanism for raising the confidence floor is discarded. |