Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Hazards, Unknowns, and Backlog — topic detail
artifact and documentation contradictions
In this document
Hazard: artifact and documentation contradictions
The earlier fleet artifact characterized D4_Orders as implementing update and delete operations and characterized D4_Report as handling backlog and stock-list reports. The more detailed source review contradicts those claims: the relevant methods only display unimplemented-option errors. The corrected interpretation is that the options and labels exist, while the underlying behaviors are not implemented in the supplied range. E0010 E0012
The earlier artifact assessment also identified a concrete stock field-interpretation error, although the supplied text does not reproduce the erroneous interpretation in enough detail to restate it safely. The supported stock fields are those defined by P_Stock: stock number, manufacturer code, manufacturer name, description, unit price, and unit description. E0010 E0013
A stated contract-gap list names D4_Stock, ID4_Orders, Orderform, P_Items, and several form classes as omitted. Those files are nevertheless present in the supplied source range. The gap list should therefore be treated as a documentation or artifact-coverage description, not as evidence that the files are absent. 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.