LEGACY EXIT FIELD GUIDE
From choosing the process to cutting over with evidence.
A practical operating map for deciding what exits, proving equivalence and preserving the way back. Every guide exposes assumptions, primary sources and limits.
Editable authority templates
- Equivalence Contract template for dual-run: A sanitized worksheet for scope, tolerances, blockers, exceptions and acceptance before cutting over a legacy process.
- Sanitized Evidence Pack template: The minimum evidence index for an auditable go/no-go decision after dual-run.
- Legacy decommissioning checklist: A cutover, retention, rollback, communication and acceptance checklist for retiring a legacy process with a path back.
1 · Selection and business case
- Choose a recurring process with reliable read access, comparable outputs, a named owner and rollback.
- Separate current cost, transition cost and post-cutover run cost.
- Keep risk and projected value distinct from realized cash impact.
2 · Equivalence and dual-run
- Version the rules, fields, tolerances, blockers and approvers before execution.
- Classify every variance as blocker, material, cosmetic, legacy defect or approved exception.
- Do not let one aggregate match rate hide a material failure.
3 · Cutover, rollback and evidence
- Rehearse the return path and measure recovery.
- Package baseline, runs, variances, approvals, access controls and the go/no-go decision.
- The current AgenticosCore demonstration is MOCK/FIXTURE; there is no client Evidence Pack yet.
Five fit gates
- Reliable and authorized read path.
- Comparable inputs and outputs.
- Rules stable enough for a baseline.
- Named operational owner and approver.
- Execution can be stopped and reversed.