Migration Guide

Key takeaways

• Migrate from prototype AI features to a governed platform in stages, moving the most risky and valuable flows into platform primitives first rather than rebuilding everything at once.
• The stages run inventory, standardize, isolate, durable, async, and govern, each with a concrete output like a Gateway route, Sandbox boundary, or Workflow execution.
• Prioritize flows that are customer-facing, high-cost, high-volume, high-risk, or hard to debug.
• A flow is done migrating only when it has an owner, route policy, runtime boundary, logs, evaluation, fallback, and incident path.

Migration should reduce operational risk in stages. Do not rebuild every AI feature at once; move the most risky and valuable flows into platform primitives first.

Migration Stages

Prioritization

Start with flows that are customer-facing, high-cost, high-volume, high-risk, or hard to debug.

Exit Criteria

Each migrated flow has owner, route policy, runtime boundary, logs, evaluation, fallback, and incident path.