Senior MQL5 Developer Needed: Porting Complex MT4 Indicator to Modular/OOP MT5 Architecture

Description:
We are looking for a Senior MQL5 Developer / Quantitative Infrastructure Architect to port a complex proprietary trading indicator from MQL4 to MQL5. 

The original MQL4 source code is available. However, because it was processed through a recovery tool, the variable names are randomized (e.g., var_116, gia_184). The core mathematical formulas, logic loops, and algorithms are 100% intact and validated. 

Critical Architectural Requirement:
We strictly require a Modular / Clean Architecture Approach (Separation of Concerns). You must not write a monolithic MT5 indicator. 
1. The Calculation Engine (Core Logic): Must be encapsulated entirely within an independent Object-Oriented (.mqh) Class Library. This engine must handle all mathematical logic (DeMark sequential counts, fractal wave calculations, sector projections) utilizing pure data arrays and MT5's high-speed buffer memory (CopyHigh, CopyLow, etc.). It must remain completely decoupled from any MetaTrader visualization code, ensuring 100% readiness for future porting into Python or C++ corporate systems.
2. The Display Layer (.mq5): A lightweight visualization layer that calls the .mqh library class to draw arrows, text, and Fibonacci objects on the chart.

Project Deliverables:
- Clean, well-documented .mqh class library containing the decoupled calculation logic.
- Clean, fully functional .mq5 and compiled .ex5 files mapping the exact visual layout of the original system.
- Side-by-side backtest verification report proving 100% mathematical signal parity between MT4 and MT5.

Screening Questions (Please answer these in your application):
1. How will you transfer data from the decoupled .mqh calculation class to the lightweight .mq5 display layer without violating the modularity? (e.g., structs, getters/setters, custom objects?)
2. What is your strategy for analyzing and refactoring recovered/messy source code variable names to ensure readability for future Python migration?
3. How do you plan to verify and mathematically prove 100% signal parity between the old MT4 indicator and your newly developed MT5 version?

To ensure the project can be easily integrated into corporate bank terminals and FIX API systems in the future, you need to deliver the mathematical core engine as a standalone Pure C++ library, simultaneously with the MT5 project.

An NDA (Non-Disclosure Agreement) must be signed prior to receiving the source file.