This is a case-study blueprint; no deployment results or customer endorsement are claimed.
Business challenge
Repeated code implements similar rules differently across an estate.
Migration approach
Identify candidate routines, their callers, input contracts, and version-specific behavior. Explain variations and propose a reviewed common implementation with explicit exceptions.
Deterministic work
Identify candidate routines, their callers, input contracts, and version-specific behavior. Record rule versions, target constraints, and unresolved exceptions; verify outputs against an agreed baseline.
Agentic assistance
Explain variations and propose a reviewed common implementation with explicit exceptions. Review generated proposals before adopting them as implementation or access rules.
Acceptance evidence
Use caller-specific regression cases to distinguish true duplication from intentionally different business rules.
Delivery time
The 34 months (estimated) assumes the stated migration inventory, accessible source definitions, available reviewers, and an agreed target environment. Plan discovery, design, build, parity testing, business review, and release readiness as separate checkpoints. Re-estimate when access, custom features, data issues, or acceptance scope changes.