Production-Ready Modernization Engine

The legacy modernization engine is now production-ready in the open source edition. This ships the full 5-stage workflow — Discovery, Planning, Migration, Validation, Cutover — with compliance gating and audit bundle export.

Full Legacy Language Coverage

The discovery pipeline now covers the full set of supported legacy languages:

• COBOL — COBOL-85, COBOL-2002, IBM Enterprise COBOL, copybook inlining
• FORTRAN — FORTRAN 77, 90, 95, 2003
• RPG — RPG II, RPG III, RPG IV (ILE RPG), AS/400
• PL/SQL — Oracle PL/SQL, stored procedures, packages
• Natural — Natural/Adabas DDMs and programs
• Assembler — x86, ARM, MIPS, PowerPC
• AUTOSAR ARXML — automotive component and composition XML
• IEC 61131-3 — Ladder Diagram, Structured Text, Function Block Diagram, Instruction List
• C/C++ — bare-metal and RTOS-based firmware

Firmware Migration Patterns

New firmware-specific migration patterns are available:

• Bare-metal C to FreeRTOS
• Bare-metal C to Zephyr RTOS
• HAL abstraction layer refactoring
• MISRA-C compliance remediation
• AUTOSAR component migration

Sector Configuration Wizard

A new wizard guides you through configuring the industrial sector for your project (automotive, medical, aerospace, industrial control). The sector selection pre-loads the relevant compliance frameworks and migration rule profiles.

Compliance Gates

Compliance gates are now enforced at each stage transition. A migration unit cannot advance from Migration to Validation without passing its assigned compliance checks. Enterprise adds approval-officer gates before regulated logic is committed.

Validation Engine

The validation engine performs fingerprint comparison between source and translated output, checking semantic equivalence within the constraints of the target language. Units that fail validation are flagged for manual review or re-translation.

Legacy Pattern Registry

The pattern registry now ships with 36 migration language pair profiles across general, firmware, and industrial categories. Custom patterns can be added by editing the registry in your workspace settings.

---

---