Virgin Atlantic · Legacy Reconfigure and Move App Quality

A Evidence level

Virginia Atlantic: Legacy re-engineering and moving App mass

Publisher: OpenAI · Vendors ' official customer information · Direct sources at the case level

Claim origin: Public disclosure by manufacturer or customer · Independent verification: No · Accessed: 2026-09-19

Evidence level measures whether a source can be located and reviewed; it does not mean vendor-reported claims were independently audited.

Standard case | Useful reference with remaining gaps 9 / 12

Business context1 / 2

Transformation workflow1 / 2

Technical workflow2 / 2

Human roles & governance1 / 2

Measured outcomes2 / 2

Source traceability2 / 2

Remaining gaps: Business context, Transformation workflow, Human roles & governance

The key to this case is not the single-point use of AI, but the re-engineering of “reconstructed and mobile App quality” to constitute an enforceable, verifiable production stream with boundaries of human responsibility.

Business problem

The aviation App online window is at high risk and it takes a significant amount of time for legacy code re-engineering and test coverage.

Solution

Use Codex to enhance test coverage, re-construct Legacy code and allow the analysis team to build the tool directly on the data warehouse.

Technical architecture & production workflow

Step 01

Large Move App Code Library + issue/ Needs + Existing Tests

→

Step 02

Codex reads the code and relies on context

→

Step 03

Generate/modify Legacy code and supplement module testing

→

Step 04

Local/CI testing and static inspection

→

Step 05

Engineer review, amendment and approval

→

Step 06

Merge into release stream; new test to improve subsequent Agent authentication

Key technology & infrastructure components

CodexContext of the coding libraryUnit TestCI/CDHuman code review

Human roles & accountability

Engineers review codes, tests and on-line; responsibility for production remains with the airline team.

FDE delivery actions

Select to release the most risky and tested project task to enter
Helping the team to connect Codex to real repo and engineering habits instead of talking in isolation.
Use test coverage as a shield for Agent's work
Let the analyst/engineering work directly in the original data and code environment
Receiving and inspection of production indicators such as re-engineering cycles, test coverage and P1 deficiencies

Reusable delivery patterns

Tests first, then expand the scope of the coding agency.
Code scenes are very suitable for the Agent closed loop of Generating Certain Tests.
Measuring top-line quality instead of just seeing the speed of code generation.

Business outcomes & delivery results

The legacy re-engineering was reduced from about 2 weeks to about 30 minutes; the new App was close to 100 per cent single-measured coverage, with 0 P1 defects at the time of issuance.

Evidence boundaries & verification notes

High: OpenAI client case publicly discloses results of approximately 2 weeks ~ 30 minutes, close to 100% single coverage, 0 P1 defects, etc.
The source can be directly located in the case; the value remains disclosed by the source and does not represent an independent audit.

Primary source: Virginia Atlantic: Legacy re-engineering and moving App mass ↗