RESEARCH • POST‑INCIDENT • CITABLE
Research Library: Provability Boundaries (Post‑Incident, Citable)
Authority posture: This research is cited inside authority records. It is not advice. It explains why authority terminates.
This research library is written for post‑incident scrutiny: when a regulator, auditor, monitor, board, or court requires proof rather than confidence.
Authority posture: These pages are cited inside authority records. They are not advice. They explain why authority terminates where deterministic guarantees collapse.
Mainframe Migration Risk: Why COBOL Behavior Cannot Always Be Proven
Pillar page. Defines provability collapse and why authority must terminate where proof ends.
COBOL ALTER Statement Risk
Why runtime-mutable control flow collapses deterministic guarantees.
Dynamic CALL in COBOL
Why runtime target resolution prevents a provable call graph.
CICS Without RESP/RESP2
Why environment-dependent error paths invalidate deterministic authority.
IMS DL/I Runtime Risk
Why IMS region state and resolution prevents replayable authority.
Limits of COBOL Static Analysis
Why confidence scores fail and fail-closed authority is defensible.
How to cite this research in an authority record
Use language such as:
This decision references Legacy Lens research (RESEARCH_LIBRARY_INDEX). The analysis explains a provability boundary where deterministic guarantees collapse. Where provability terminates, authority terminates under the declared governance context.
Explicit non‑claims
- This research does not predict runtime behavior.
- This research does not certify compliance.
- This research does not recommend remediation steps.
- This research defines evidentiary limits only.