SELECTED WORK · SEVEN PRODUCTION SYSTEMS
Seven production systems. Every claim carries a number.
Every number below reconciles: a public replay command, or an inline NDA note. Every engagement was production under NDA; the public artifacts (COBOL probe, LLM adversarial gate) are deterministic synthetic reproductions of the findings — clone and run.
Work with me →Found in 127 minutes. After 3 years of clean standard audits.
Payroll batch system: COMP-3 fixed-point truncation compounding below the reconciliation threshold, invisible to sum-level checks. Internal audit: PASS. Every quarterly review: PASS. Adversarial probe: found. Production engagement, NDA (the public cobol-pic-probe reproduces the failure class on a synthetic, fixed-seed corpus, not the client’s data). Clone and run.
Evidence artifacts →From $26,400/mo. Air-gappable. SHA-256 hash-chained. Zero managed-API dependency.
2-node Exo distributed inference cluster. M1 Max 32GB + M4 Mini 16GB = 48GB unified memory pool. Thunderbolt 4 inter-node <0.4ms RTT. SHA-256 hash-chained outputs on every inference request. 55 commits ahead of upstream on a production fork of Exo. HIPAA-compatible (zero PHI egress) architecture. Self-healing: drift and health oracles with auto-recovery daemons keep the ring and its knowledge store fresh with zero human touch — 99.97% measured uptime over the 12-month window.
Cluster details →Zero false negatives. Public corpus n=220 (140 adversarial + 80 benign): 140/140 caught, 0/80 over-blocked — clone and run. MITRE ATLAS threat model. Embedding drift caught 3–7 steps early.
Multi-agent validation gate on every LLM output. 5 OWASP LLM Top 10 classes covered. Zero incidents across the measured window.
Evidence artifacts →Throughput. 5,200 lines → 2,000 Rust. 464 tests. 0 known CVEs introduced (dependency-scanned).
Production batch pipeline rewrite. IEEE 754 compliance maintained throughout. Byte-exact deterministic replay against original COBOL output. Every arithmetic edge case verified. 18-month zero-downtime strangler-fig migration; core batch rewrite complete in one quarter.
Evidence artifacts →All three final NIST PQC standards mapped for migration readiness. ML-KEM · ML-DSA · SLH-DSA. Advisory, not a deployed implementation.
Post-quantum migration readiness across all three final NIST algorithms: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA). HSM-bridge architecture mapped; CISA harvest-now-decrypt-later exposure assessed. Advisory, no deployed implementation claimed.
Evidence artifacts →Full dependency graph, any codebase. SHA-256 hash-chained. Zero manual nodes.
Automated code dependency and call graph extraction. Every import, every call, every edge: no annotation, no manual mapping. Dead code detection, circular dependency tracing, attack surface mapping. Runs across all of it: COBOL audits, LLM integrations, M&A diligence, red team prep.
Graphify details →Deterministic audit-trail artifacts, mapped to production systems.
Production artifacts: quality management system, bias documentation, human oversight logs, adversarial validation records, SHA-256 hash-chained chain-of-custody — engineering artifacts, not a legal opinion.
Evidence artifacts →WHAT THE GREEN DASHBOARD HIDES · SEVEN SILENT FAILURE MODES
Seven findings below. Each one is left undetected by standard audit procedures — the adversarial method surfaces it. Each ships with the replay command that reproduces it.
Deterministic COBOL forensics, sovereign on-device inference, and signed model-risk attestation sit in three separate hiring lanes. One engineer covers all three here.
- PIC V9 truncation compounds below the reconciliation threshold (the payroll finding above); the public probe reproduces it byte-for-byte.
- Embedding drift degrades LLM output 3–7 steps before it shows up in any production metric.
- A timestamp signs the request; nothing proves the bytes. An unsigned inference cannot be reproduced or attributed.
- Managed-API spend reads as capability when it is vendor lock-in, and it is removable to $0 API cost by self-hosting (hardware/power still apply).
- COBOL→Rust rewrites diverge on arithmetic edge cases unit tests miss entirely. Byte-exact replay against original output catches every one.
- Post-quantum migration reads as deferrable until harvest-now-decrypt-later has already closed the window.
- Engineering artifacts: reproducible, SHA-256 hash-chained chain-of-custody — for compliance validation, work with your counsel.
Each finding ships with a deterministic replayCmd and a signed audit-log entry. Clone, run, reproduce the number yourself. First three, verbatim:
WRITTEN SCOPE FIRST · MILESTONE-GATED · REPLAY-VERIFIED
Three questions. If your team cannot answer all three, one of these seven findings is active.