Application examples
Inspect source-checked findings from real application code.
Each example separates what the evidence supports, the engineering decision it creates and what still needs review.
COBOL · CICS · VSAM · Batch processing
Inspect balance settlement, concurrent card edits and batch rejection behaviour. Follow the findings into specification decisions and a proposed .NET and TypeScript plan.
Analysis, specification and proposed plan
Examine CardDemo →.NET Framework · C# · SQL Server
Inspect workflow-specific dates, financial-guarantee transitions and their relationship to movement eligibility. See what the specification review must resolve before planning.
Reconstruction and specification review
Examine PRSD-IWS →Natural · Adabas · Mantis · Supra · JCL
See what Wayfinder established from an unfamiliar public synthetic legacy corpus in approximately an hour, what remained unresolved and how the gaps become the next evidence set.
Published case study · public benchmark
Read the case study →For each finding, examine the behaviour, its source and the consequence of changing it. The proposed checks show how a team could test the decision. They are not presented as executed tests.
These are public-source worked examples rather than customer case studies. Source links identify the exact revision used for the selected checks. Full application acceptance remains separate.
Recursive Application Denoising describes the PRSD reconstruction and its limits. Poor productivity is often a function of legacy explains why incomplete system knowledge consumes delivery effort.