Transparency without invented certainty
Know what evidence is visible and what commercial secrecy leaves unanswered.
Useful disclosure
A seller can explain decision scope, feature timing, retraining and validation without publishing every commercial parameter. Request those boundaries rather than treating either secrecy or an open code repository as a complete quality verdict.
Inspectable is not validated
Visible code can still leak future information or use unrealistic execution assumptions. Conversely, an opaque system can have account evidence relevant to a particular return claim. Match each conclusion to what was actually checked.
Classification
Describe an unknown architecture as unknown. Describe untested capability as documented capability. No platform, model family or distribution channel receives a universal profitability verdict from this desk.
Sources
- QuantConnect optimization parameters
- ALFRED real-time and vintage data
- OpenTimestamps protocol documentation
Research guides
AI data leakage and holdout audit
Audit feature availability, outcome overlap and test exposure with a frozen experiment record and a worked calendar-boundary example.
Backtest, forward and live evidence
Reconcile simulated decisions, prospective instructions and account fills without promoting one evidence layer into another.
Algorithmic versus AI signal claims
Map fixed rules, trained predictions, AI explanations and order routing to the specific consumer evidence each needs.
Transparency and evidence have different denominators
A publicly readable rule can still be selected after extensive exposure to past outcomes. A proprietary model can supply a bounded independent review without revealing every weight. The buyer should ask what was actually inspected and which claim the record supports rather than treating openness as a universal profit verdict.
A fictional packet supplies a feature contract but no data membership or original output history. The reviewer can describe that contract and identify the missing evaluation, without declaring it either fully validated or fraudulent. The feature-importance and artefact chapters add concrete questions about explanations, versions and reproduction. No feature page is promoted into an account audit.