What the dated record contains
The saved 21 September Sensor Flarex Xp page combines decision-support, copy-trading and autonomous language with a statement that it does not take orders. Those descriptions leave an important boundary unclear. We have not authenticated the operator or observed the software. This is a question raised by public wording, not a report that a customer's instructions were mishandled.
Write down where your decision would end and automation would begin
A useful personal note could describe one action you expect to approve and what you think will happen next. Ask the provider to confirm or correct that sequence in writing. Who can act after the approval, and what would require a new decision? Keeping the expected boundary explicit makes it easier to spot a mismatch later. The example is a way to request clarification, not proof that these options exist for this name.
What would make the decision clearer
An attributable agreement and a consistent explanation would be needed before assessing actual behaviour. We have not copied a strategy, authorised a trade or used a stop control. No performance or safety verdict can be inferred from the conflicting descriptions alone. Unknown keeps the unresolved scope visible, while the decision note prevents the reader's own interpretation from being mistaken for a promise the provider has documented.