Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Hazards, Unknowns, and Backlog — topic detail
Evidence and coverage limitations
In this document
Hazard: Evidence and coverage limitations
The supplied analyses identify retained source coverage not represented in earlier summaries, including ID4_Globals.java.svn-base, Order.java.svn-base, Orderform.java.svn-base, P_Ordcur.java.svn-base, State_List.java.svn-base, Stock1.java.svn-base, Stock_Sel.java.svn-base, and several SVN metadata/property files. Consequently, conclusions about order-entry UI, stock UI, state selection, and form completeness remain incomplete. E0004
The expected Customer.java.svn-base contents are not present in the supplied evidence shown for the broader range, so its behavior cannot be independently assessed there. Four legacy form files—demo/source/cust.frm, custcur.frm, custform.frm, and customer.frm—were not analyzed as text because they contain NUL bytes or unsupported encoding. Their listed sizes and hashes are provenance for unavailable artifacts, not evidence of their behavior. E0006 E0007
Files under .svn, including entries, all-wcprops, and prop-base/*, are Subversion working-copy or provenance metadata. Repository URLs, revisions, and executable properties do not establish application features or runtime behavior. E0004 E0006
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.