The current pilot has enough graph, artifact, and workflow coverage to support a credible modernization readout.
Attention
One workflow still carries elevated routing risk
Notice-selection behavior remains the highest-value path to stabilize before broader refactor work begins.
Next best move
Expand test generation coverage
Increasing characterization breadth is the fastest way to reduce uncertainty before touching duplicate branches.
Command center
Ask the system what the old code actually does
Query resolved
Which modules calculate late-payment penalties and update downstream customer notices?
Resolved insight
4 COBOL programs and 2 JCL jobs contribute to the penalty flow. One downstream branch still bypasses the updated notice renderer for legacy account classes. Duplicate penalty logic appears in two separate modules, increasing change risk.
Recommended next step
Generate characterization tests for both branches, wrap notice selection behind a service boundary, then consolidate duplicate business logic.
Move between the product workspace and the customer-facing story without losing context. The public site now mirrors the enterprise intelligence framing of the app.