For engineering teams who verify a claim by running it
Project, COBOL, COMP-3, Mainframe
COBOL Forensics & Modernization Engine
COMP-3 Boundary Discovery — Public synthetic probe: $40,832.41, clone & run
Mainframe systems running decades-old COBOL codebases can contain undocumented COMP-3 packed-decimal boundary conditions that cause silent data corruption. Detecting these requires manual byte-level forensic analysis, tooling most audits skip.
The Problem
Mainframe systems running decades-old COBOL codebases can contain undocumented COMP-3 packed-decimal boundary conditions that cause silent data corruption. Detecting these requires manual byte-level forensic analysis, tooling most audits skip.
Approach
Built an automated COMP-3 / PICTURE-clause boundary analysis toolchain. Adversarial audit methodology: inject boundary conditions at field level, trace propagation through batch processing chains, surface any silent truncation or overflow. The failure class is reproduced publicly on a synthetic, fixed-seed corpus — clone and run cobol-pic-probe ($40,832.41 compounding loss, 47,312 records, no client data).
Proof Metrics
Want this on your team?
This work maps to 4 qualifying roles. Remote, open to mid-level and senior IC roles.