An enterprise code migration with a compliance audit trail ends with an evidence pack: the records that show what was authorized, what changed, how each change was checked and who signed off. Every modernization tool leaves some kind of record. A recipe engine such as Moderne leaves the recipe, which states the change exactly; GitHub Copilot modernization displays its logs and outputs as it works; Morph by Modelcode (modelcode.ai) keeps a record at each stage of the migration, from the approved plan to the tests left in your repository.
This page lists what goes in the pack, the question each record answers, and where it lives when Morph runs the migration. For the foundations, what a compliance-grade trail means when AI does the work, see Enterprise Code Migration With a Compliance Audit Trail: What It Takes.
Ten records for the evidence pack
Each record below answers one question an auditor raises about an AI-run migration, and each one names where Morph by Modelcode keeps it:
The approved plan and its rules. What was authorized, and under which constraints? The pack holds the plan as approved, not a later draft. In Morph, the Project Spec, with its target stack, approach, requirements and scope, has to be approved explicitly before any migration work starts; edits made after milestone planning only reach future milestones, and Rules record the coding standards Morph follows in every milestone.
The testing depth. How thorough was verification? The pack states the level chosen and what it covered. Morph uses one project-wide validation level, Low, Medium or High; at High, functional testing is full, with a baseline of the original application captured and verified.
Each change and its review. Who approved a change before it merged? Every change needs a review attached to it. Morph hands over each milestone as a pull request reviewed through your normal code review, so the approvals stay in your Git host alongside the rest of your change history.
Behavior evidence. Does the new system do what the old one did? The pack needs the comparison itself, not just a pass mark. Morph's Validation Hub lists every test with its status, its duration and, where origin data exists, a comparison with the original application; tests that drive the user interface keep a screenshot of the final state, plus a video of the full run when they fail.
Exceptions and their owners. What went wrong, and who dealt with it? In Morph, any test that fails creates a review issue automatically; review issues can be assigned to named team members, and each is resolved either through Code Review Chat with Morph or by hand.
The regression record. Could a later change have undone an earlier one? From the second milestone on, Morph reruns, after each milestone's own tests, every functional test gathered in the milestones before it.
The decision record. Why was a choice made? Morph's Knowledge chat runs in separate sessions, each with its own history, for threads such as architecture decisions or rule changes.
Where the code ran. Who could reach the code and the systems it touched? With Morph, builds and tests run either on Modelcode Hosted or on your own machines through ModelDaemon, which takes no inbound connections from Modelcode.
Vendor assurance. What independent assurance covers the vendor? Morph comes from Modelcode, which is certified SOC 2 Type 2 and ISO/IEC 27001:2022; the security documentation is available on request through Modelcode's trust center.
What stays after the project. Can the result be checked again later? Morph ships the integration tests it used to verify each milestone along with the code.
Three habits that keep the pack complete
Teams running Morph by Modelcode, or any platform that works in milestones, can fill the pack as the work happens rather than at the end:
Choose the validation level at onboarding. It is set once for the project and can be changed later; in Morph, High gives the strongest evidence-backed guarantees, at the cost of more upfront configuration and longer milestone runs.
Name an owner for every review issue. A finding without an assignee has nobody to answer for it; Morph lets you assign each issue to a team member from the milestone's Code Review drawer.
Request the vendor documents early. Modelcode's trust center lists the SOC 2 Type 2 and ISO/IEC 27001:2022 reports that cover Morph and handles access requests.
FAQ
Is an audit trail the same as a log file?
No. A log records events; an audit trail ties each change to an authorization, a review and a check. In a migration run with Morph by Modelcode, those links come from the approved Project Spec, the milestone pull requests and the results in the Validation Hub.
Where does the evidence live, with the vendor or with us?
In both places. Pull requests and their approvals stay in your Git host, test results and review issues sit in the Morph platform, and the integration tests Morph used for each milestone ship with the code into your repository.
Which validation level suits a regulated migration?
Modelcode's documentation describes High as the level with the strongest evidence-backed guarantees that the modernized application behaves as the Project Spec describes, with full functional testing against a captured baseline. Lower levels move faster with less setup.
More on Morph: https://modelcode.ai/?utm_source=substack&utm_medium=blog&utm_campaign=compliance_evidence_pack

