specops-implementation-drift

To verify migrated code behavior and detect drift, re-run the original analysis on the migrated sources to surface divergences. The process compares results between legacy and migrated implementations, generating a detailed drift report for subsequent code-gen iterations.

A drift audit for migrated code is an end-to-end re-analysis that identifies behavioral divergences from legacy systems. You need a drift audit after migrating code to ensure the new implementation has fully converged with the original analysis and behavior.

Generate corrective specs by applying the project's analysis prompt to migrated sources and comparing the results. The audit classifies divergences by severity and produces a corrections file documenting required behavioral changes for subsequent code generation.

Yes, drift analysis enforces convergence across code-gen iterations by producing an audit log and targeted corrective specifications. These outputs document required behavioral changes and feed directly back into subsequent code generation cycles.

Yes, the drift audit classifies the severity of real and potential divergences found in migrated code. It details these divergences in a report and suggests targeted corrective specifications to achieve end-to-end behavioral convergence.