Observed source material
The shared 21 September records show a .org FAQ describing risk controls, .online terms excluding execution and custody, and a .live trading-business narrative. The investigation did not establish that one company owns or supplies all three. These documents describe different public claims; they do not demonstrate an implemented system or an authenticated account relationship.
A technical feature must be linked to the same service terms
For a technical brief, each feature needs a clear product boundary. Ask which domain's agreement covers the feature and which party supplies the action it describes. If a control is informational only, it should not be tested as though it executes an instruction. If another service performs the action, that connection needs its own specification. These possibilities are questions raised by the sources, not architecture verified here.
Requirements for further verification
A consistent manual, provider identity and applicable contract would allow a later review to select an appropriate test. We have not enabled a safeguard, inspected a private dashboard or measured execution. Unknown therefore reflects missing linkage between claims and an actual product. No feature from one domain is used to fill another domain's documentation gap, and no advertised operating history or return is adopted as a verified result.