Verified Trading Signals

Complete signal populations and proof coverage

Reconcile identities and status rules before interpreting a proof percentage.

Editorial revision: 14 October 2026

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

Choose the population before the sample

A completeness claim begins with a product, version, channel, timezone and continuous date range. It needs original stable IDs, not just a count printed on a dashboard. Define whether the population contains published ideas, activated entries or completed positions. These sets differ. If a service offers several models or paid tiers, identify which subscribers could receive which original calls instead of combining incompatible channels into one impressive total.

Write the inclusion rule before examining success. Otherwise a losing idea can become unactivated while a similar winner becomes eligible. Keep cancellations, expired calls and open positions visible. A published call that did not fill is not a winning completed trade, but it may still belong in the original signal population.

Counts expose only some problems

The worksheet assumes mutually exclusive winner, loser, flat, open, unfilled and pre-fill-cancelled statuses. Their sum should reconcile to the declared original total. A positive gap means records are unclassified under those assumptions; a negative gap means the entered statuses exceed the population. Neither sign identifies the exact cause. It may reflect duplication, inconsistent definitions or a wrong date boundary.

A zero gap is not enough. In an invented four-ID population, duplicating ID B while omitting ID C preserves the row count. Only ID-level reconciliation reveals the swap. Compare the original set to the status ledger, flag duplicate identities and retain version relationships. Amendments should normally remain linked to one original call rather than increase the original-call count.

Proof coverage has its own denominator

A commitment percentage counts calls claimed to have committed bytes. An anchored percentage counts the subset claimed to have a verified external attestation. They should not be presented as identical. The worksheet enforces anchored count no greater than committed count and committed count no greater than originals, but it does not verify any of those statements. User-entered percentages are bookkeeping diagnostics, not a quality score.

Coverage also needs field scope. Ninety entry-only commitments do not become ninety fully specified exit plans. A proof that binds a grade and entry leaves uncommitted stops and targets unresolved. Track required fields and proof state per ID when conducting an actual audit. Report sampled and complete-field coverage separately instead of blending them into a single trust badge.

Link outcomes without inventing execution

Join original IDs to execution records, amendments and terminal states using a declared policy. A cancellation after a fill belongs to a different event chain from cancellation before any execution. Quantity-weighted partial exits can make a target hit a flat or losing net position. Costs and open exposure require their own treatment. A complete message archive is therefore necessary for some claims but insufficient for a complete performance calculation.

Publish the unresolved-ID list, duplicate check, status definitions and proof-state map alongside any resulting summary. Explain the closed-win denominator, including flats, and retain the full original population for operational review. Do not extrapolate a clean sample into verified full history. The most useful outcome can be a bounded statement: these IDs reconcile under these rules, these proofs were actually checked, and these execution or chronology questions remain unanswered.

A duplicate-ID exercise

Take four fictional original IDs A, B, C and D. Construct four status rows A, B, B and D. Counts agree, yet one original is absent and one is duplicated. Write both discrepancies before computing any percentage. Replace the duplicate with C only in a separately labelled corrected fixture; retain the erroneous original to demonstrate the failure mode.

Then mark two calls committed and only one externally anchored. Keep separate denominators and explain which original IDs each claim covers. Add an amendment linked to A without increasing the original count. This fixture tests bookkeeping and identity policy, not actual proof validity. A complete provider review still requires original artifacts, verified field scope, chronology and execution evidence rather than the neat totals produced by an invented example.

Source documents

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

Continue the investigation

Signal population reconciliation

Put this question beside the populated packet

Use the eight-ID practice packet to retain the distinction this page makes. Inspect the original roster, record labels and amendment graph before quoting a complete-period percentage. Compare the authored byte variants when the question concerns representation. For a timing question, keep the declared deadline and uncertainty together rather than borrowing a later outcome. These exercises have no authentic provider proof or economic ledger. They teach bookkeeping and scope; they cannot close a real evidence request. A new review would need genuine original files, a performed transcript and separately inspected delivery or execution records.

Open the populated review packet