AI-automated attribute lineage documentation

The core Oracle system holds the customer's contract and partner data, communicating externally via the CEISeR web service catalog (SOAP, WSDL/XSD). Three access paths must be considered for the pilot attribute 'partner phone number': the A-path (core system as provider), featuring two reciprocal operations within the same service; the E-path (core system as consumer), which is not visible in any core system WSDL; and an internal batch process. The same business attribute bears a different name at each of these three storage locations. Implementation takes place exclusively within the A and E packages. The analysis utilizes a realistic PL/SQL test corpus spanning two schemas and containing deliberately erroneous test data. The evaluation proceeds in two stages: a first run captures each attribute in a graph structure (JSON), while a second run generates a report for each attribute based on this data. In the absence of precedence rules in the code, the attribute is persisted at all three storage locations.