In plain language
A black box is a system whose inputs and outputs are visible but whose user lacks enough information to understand how signals are produced or what limits their use.
Opaque in what respect
Opacity may concern data, rules, parameters, costs, conflicts, controls, or the conditions under which the system is overridden. Source code is not always required for operational assessment: objective, universe, frequency, risk, verifiable history, versions, and oversight may be more relevant.
What it does not prove
Closed source and black box are not perfect synonyms. A proprietary product may document its behavior and limits; open-source code may remain unintelligible or unvalidated. A black box does not by itself prove fraud or poor performance. The label identifies a constraint on verification.
Minimum checks
Before connecting capital or credentials, check provider responsibility, data used, order logs, costs, testing, monitoring, and shutdown procedure. Quantitative trading covers validation; Anti-scam provides provider checks.
Sources
- U.S. SEC, Robo-Advisers — IM Guidance Update 2017-02 — Lists algorithmic risks, limitations, oversight, third parties, and override conditions that should be disclosed.
- FINRA, Know the Risks of Auto-Trading Services Offered by Unregistered Entities — Advises users to question vague technology claims and verify providers, performance, and access to data.