MQL5: Development of a Core Risk Management Module (FIXED MAX LOSS PER TRADE GUARANTEE)

Project Overview:
We are seeking a highly skilled MQL5 developer to create a core, standalone Money Management (MM) module. This is *not* a request for a full trading strategy, but a fundamental safety component that must be mathematically precise and error-free.

The primary objective is to implement a robust FIXED MAX LOSS PER TRADE function, which is the cornerstone of our capital preservation strategy.

Phase 1 Requirements (Non-Negotiable):

1.  Fixed Max Loss Guarantee (Core Function): The module must calculate the precise lot size for *any* given trade (BUY/SELL) based on two user-defined inputs:
    *   Input A (Safety): User-defined MAXIMUM DOLLAR/EURO LOSS per trade (e.g., $50, €100).
    *   Input B (Exit): The actual, dynamic distance to the trade's Stop Loss (SL) level in points/pips.
    
    The resulting Lot Size must GUARANTEE that if the SL is hit, the realized loss is EXACTLY the value of Input A (Max Loss).

2.  Precision Calculation: The calculation must accurately account for the instrument's Point Value (currency conversion) to ensure dollar/euro precision.

3.  Broker Compatibility: The module must work seamlessly on ECN/STP accounts and accurately handle dynamic Stop Loss distances.

Key Developer Filter (Mandatory Question for Application):

*   Crucial Test: We require an explicit confirmation that the developer understands that the Lot Size must be inversely proportional to the Stop Loss distance (i.e., a wider SL must result in a smaller lot size to maintain the fixed dollar risk).
*   The Problem We Are Solving: The developer must confirm they understand that we are avoiding the fatal flaw in public EAs where "Risk %" is merely a Lot Multiplier unlinked to the SL.

Budget: $200 - $350 (Depending on complexity and developer rating)

Timeline: 5-7 Days for initial module delivery.

Next Steps: Please provide a brief explanation of how you would approach the lot sizing calculation (the formula/method you would use). We will only proceed with developers who clearly understand the FIXED MAX LOSS principle.