Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Informix 4GL case study
Reference scope and confidence
In this document
Reference scope and confidence
This reference covers the supplied source and second-opinion analysis for the stores demo. The evidence is bounded rather than lossless: one supplied range covers source bytes 0 through 184066 with SHA-256 39e4d96114d221c32f3724f519fd0d94e89a1c029ccdb94b228ac8222c923e13, while an earlier artifact assessment covers a separate complete range of 99227 bytes. Per-file byte offsets were not supplied, so findings are identified by filenames, methods, and symbols rather than invented offsets. Exact source coverage does not establish semantic completeness or correctness. E0010 E0012
The strongest findings are high-confidence observations of the main menu and module structure, shared global state, bounded loading of state and stock data, the visible transaction structure of order creation, and the unimplemented stock, backlog, order-update, and order-delete options. Swing-like UI behavior, report lifecycle concerns, and equivalence between the two 10-percent total calculations have medium confidence. Customer behavior, database schema details, framework status semantics, exception rollback, command-execution scope, query sanitization, report buffering, and concurrency safety remain unresolved. E0012
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.