How Decode, Praxent’s reverse engineering agent system, modernized a critical, end-of-life Delphi reconciliation system processing $2B per day.




The platform, written in Delphi, managed exception ticketing, executed funds movement, and carried seven-year data retention obligations. A single drive failure or bad reboot created a real probability the system would never come back up, and manual reconciliation at that volume was not an option.
The compiled language can no longer be licensed. Rebuilding the system was not an option without the tools to compile it.
The OS running the platform was no longer receiving security patches or vendor support.
The physical machine in the data center could not be replaced. A drive failure with no path to
recovery.
Every engineer who built the system
had left. No documentation existed outside the source code itself.
Ever y file fingerprinted and scored on a six-factor complexity model.
Blueprint of every class, form, API surface, and module.
Full dependency graph with circular-dependency and coupling-risk reports.
Every record, class, and database schema mapped with code-to-SQL traceability.
Calculations, validations, and
SQL intent recovered line by line. 143 SME questions raised and prioritized.
Findings organized across seven business domains with traced requirements and user stories.
SME answers folded back in, producing implementation-ready requirements with full traceability.
Cross-checked against source code, database structures, and documented system behavior.

Every phase of Decode has a Praxent forward-deployed fintech engineer in the loop. They calibrate scope, interpret findings against payments patterns, decide which of the SME questions need human input, and translate the recovered logic into a build plan compliance can sign off on. That loop produces specs you can act on.

EXAMPLE BUSINESS RULE EXTRACTED
The bank statement balance is calculated as the sum of all line item amounts for the statement period, but only for top-level items where the parent line item is null or 0. Detail and child line items are excluded to prevent double-counting.
Legacy modernizations break in the third month of production when a business rule no one remembered surfaces incorrectly. Decode pulls those rules out of the source first. SMEs validate them before the build starts. Parity comes faster, with less risk.

stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
Modern security vulnerabilities, exploited by AI-powered attack tools, are making 20-year-old codebases even more exposed. The risk is getting higher. And the barriers are getting lower.

stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
stored in source, visible to any developer with repository access.
Pre-implementation
Implementation phase
Tested against synthetic, real, and historical data. Differences become test failures.
We're in an era where you can fully understand and rebuild parts of your system that are slowing you down. When you can do that for a fraction of the cost, you fundamentally reevaluate what legacy means and how it is affecting your velocity as a business.

