migration-seams

Turns a system map into migration decisions: scores risks, finds coupling hotspots and shared-data traps, identifies safe migration seams, assesses deployable readiness, compares migration options, and sequences candidate migration slices. Use as the risk-and-seams phase of legacy-code-discovery, or standalone when asked what could break, what must move together, where to start a migration, how to split a monolith or legacy service, or which risks threaten cutover. Prefer legacy-code-discovery when the request spans more than one phase or needs a durable bundle. Not for code review, architecture aesthetics, or selecting a destination stack.

Compatibility

Requires read access to the target repositories and write access only to the discovery bundle. Consumes a system map from system-cartography; bundle conventions live in legacy-code-discovery/references/okf-bundle.md. Read-only production queries, characterization tests, and spikes all need explicit approval; anything that writes or replays live traffic needs a disposable environment.