Verified Trading Signals

Trade Ideas: proof scope and population coverage

Scanner population before selected output: source-specific evidence questions for Trade Ideas, not a completed paid-account test.

Editorial revision: 14 October 2026

Scanning software. A documentation-based note, not a measured performance ranking.

Verification methods and user-led checklists. No provider has been certified by this site; declared coverage counts are not independently checked.

Scanning software

Scanner output needs a complete candidate population and a frozen rule. Selected examples cannot prove coverage.

Evidence still needed

Request original bytes, serialization version, proof file, verified attestation, complete signal-ID population, amendments and the separate execution ledger. A hash match is only one part of that request.

Assessment boundary

No paid-account test, complete trade population or independent execution comparison was supplied for this entry. Current terms, regional eligibility and the exact purchased offer require direct confirmation. No rating, rank or consumer-review count is asserted.

Source documents

Documentation establishes the stated mechanism, not tested trading performance. Checked 9 October 2026; a later version can differ.

Scanner population before selected output

Request the configuration, source-data version, scan clock and all eligible candidates under the exact rule. A highlighted successful candidate does not define the complete scanner population. Keep exclusions, unavailable instruments and changed thresholds visible. These are evidence requests; the publication has not run a paid scan or measured candidate performance.

Separate research and execution

Identify whether a result is an idea, simulated strategy, discretionary selection or actual order. A file commitment can cover configuration or candidate output without establishing broker fills. Join only under genuine stable identities. A model-validation claim needs its own frozen method and independent evidence; digest reproduction cannot supply those tests.

An invented candidate-selection exception

Create fictional scan run R4 with eligible candidates C01, C02 and C03. A demonstration page shows only C02 after its favourable move. Even if the displayed C02 file has a reproducible digest, that artifact cannot establish the missing candidates or the original eligibility rule. Preserve all three original identities and the scan cutoff rather than redefining the denominator to one attractive example.

Suppose a later configuration R4-v2 changes a threshold. Link the new settings to the original version and keep their effective-time question open. A digest of the settings answers configuration identity, while a digest of candidate output answers a different object. Neither proves the data were timely available, that an order was submitted or that the selection generated a net subscriber benefit. These are authored record labels, not a scanner test.

Retain run_id, configuration_digest, data_version, universe_definition, scan_time_source, candidate_id, inclusion_rule, exclusion_reason and any decision/order join. A strategy-validation claim would need a separately frozen evaluation method and independent observations. The file checker and ID packet do not provide those samples. In this example the bounded finding is that one selected candidate is inspectable while original-run completeness remains unresolved. That conclusion can support a useful evidence request without inventing a performance rank, win percentage or benchmark comparison.