Wayfinder / Case study / Diagram galleries

Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: Deployment evidence

Deployment evidence

In this document

What is deployed where, and is that known from repository declarations or a verified runtime observation?

This view separates repository artifacts from deployment targets. The supplied material reports 4GL form definitions, compiled .frm files, Java target source, and declarations of the stores7 database, but it does not provide a source declaration or runtime observation assigning any of them to a host, environment, server, or verified runtime target. E0009 E0010

The .per files support repository-level form definitions; they do not establish that the corresponding compiled .frm files are identical or were generated from them. E0010 The reported database name is a repository declaration, not evidence of a deployed database endpoint or connection target. E0009 Consequently, no deployed_to relationship is asserted.

Elements

4GL form definitions

Kind: component
Basis: reported
Description: Repository form definitions include ordcur.per, order.per, orderform.per, p_ordcur.per, state_list.per, stock1.per, and stock_sel.per; these declare screens, fields, database names, and table mappings. E0009
Evidence: E0009

Compiled .frm forms

Kind: component
Basis: reported
Description: The corresponding ordcur.frm, order.frm, orderform.frm, p_ordcur.frm, state_list.frm, stock1.frm, and stock_sel.frm files are reported as binary or NUL-containing and were not analyzed as text. E0009
Evidence: E0009

Java target source

Kind: component
Basis: reported
Description: Repository Java target source includes D4_Cust.java and D4_Demo.java; the evidence describes customer operations, UI menu registration, and access to application modules, but does not establish deployment placement or semantic equivalence with the displayed 4GL sources. E0009 E0010
Evidence: E0009, E0010

stores7 database declaration

Kind: component
Basis: reported
Description: Multiple 4GL programs and form definitions declare a database named stores7. This establishes a repository-level database dependency, not a deployed database host, environment, endpoint, or verified runtime connection. E0009 E0010
Evidence: E0009, E0010

Relationships

Gaps

No deployment target is evidenced for the 4GL form definitions, compiled .frm forms, Java target source, or stores7 database declaration. The supplied material contains neither a repository deployment declaration nor a verified runtime observation assigning these components to a host or environment. E0009 E0010

The relationship between each .per definition and its compiled .frm counterpart remains unresolved; the binary files were not available for text analysis, and their reported hashes identify artifacts without validating generation history or semantic identity. E0009 E0010

The database evidence does not establish the actual endpoint, credentials in use, hosting environment, or whether the declared stores7 database is reachable at runtime. E0009 E0010

Follow-up requires deployment manifests or configuration that explicitly assign components to targets, plus runtime observations for the active environment and verification that compiled forms correspond to the supplied definitions.

Recovery limitations

  • No supported relationships reconstructed.
  • Required concepts not established: target
  • Some identified concepts have no supported connection.

Sources

  • E0009 — SHA256 c4ffb94922eae3cda2f1c6d6b1215da47b424d41fea52db3870783bd43051b30
  • E0010 — SHA256 bd29371182d16de63a7651533fa5c84e151a01ea9bf23399f7f6ca0397ab0250