Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Hazards, Unknowns, and Backlog — topic detail
Documentation and source authority
In this document
Hazard: Documentation and source authority
The analysis identifies stale documentation that should not be treated as executable truth. The secondary fleet description is useful as an inventory, but it overstates behavioral certainty and contains the concrete stock.unl field-order error. Structural claims such as form mappings, menu labels, and file availability may be supported while claims about runtime correctness, semantic equivalence, or successful transitions remain contradicted, conditional, or unresolved. E0008 E0010
Known labels such as Add, Update, Delete, Modify, and Exit establish available commands, not that every command succeeds or produces the expected state. In particular, a declined deletion can produce “Record deleted” feedback without deleting the row, and a rejected or empty lookup is not evidence that an order was successfully selected. E0010
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.