How should break-even logic be automated safely?

What this means in practice

Break-even needs an explicit trigger, new stop, optional positive offset, precision rule and one-time/repeat behavior. It must also handle partial positions, gaps and broker stop constraints. This page is specifically about “How should break-even logic be automated safely?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Exact entry BE

Define activation threshold and protected price explicitly. Once stronger protection is active, never move the stop backwards; after partial fills or reductions, use the actual remaining position state. For Scenario A — Exact entry BE on question 84, use that evidence specifically to answer “How should break-even logic be automated safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — BE+offset

Define activation threshold and protected price explicitly. Once stronger protection is active, never move the stop backwards; after partial fills or reductions, use the actual remaining position state. For Scenario B — BE+offset on question 84, use that evidence specifically to answer “How should break-even logic be automated safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Partial position

Inspect the mechanism named by “Scenario C — Partial position” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Partial position on question 84, use that evidence specifically to answer “How should break-even logic be automated safely?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• symbol metadata and unit conversion
• configured risk or management rule
• broker min/max/step or distance constraint
• normalized value actually sent to cTrader

Practical rule

For “How should break-even logic be automated safely?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.