Consumer research
Telegram signal results: messages are not trade denominators
Reconcile setup families, updates, cancellations, unresolved cases and conditional outcome rates in a finished fictional ledger.
Freeze the population definition
Decide what creates an originating setup and what updates an existing one before seeing the outcomes. A channel can produce several targets, amendments and recaps for one idea. Counting each positive update as an independent success while leaving losses at the setup level changes the measurement object. Keep a message count alongside a setup-family count rather than choosing whichever looks better.
A complete expected population requires a defined source, tier and observation period. Public previews and paid-room originals may not be the same population. Unknown missing instructions prevent a full-population claim even when the visible sample is easy to count. Preserve the boundary instead of presenting a screenshot collection as the entire service history.
Keep distinct terminal and open states
A resolved positive outcome, negative outcome and zero outcome are different from a cancellation or an unresolved setup. The declared method decides which enter a conditional outcome-rate denominator. Keep excluded cases visible and state why. A cancellation is not a win, while a missing close is not automatically zero. Count open cases without supplying invented final prices.
Partial targets need a position rule. Three hit-target announcements need not mean three completed trades. Without quantity allocations and the final close, gross contribution may be unresolved. A correct count of announcements cannot establish an account return, drawdown or net expectancy. Those measures need their own records and capital conventions.
Do not infer money from a win rate
A high positive-outcome fraction can coexist with a negative contribution if losing outcomes are larger. Account fees, slippage, financing, open exposure and sizing add more distinctions. A raw sum of outcome labels cannot become compounded account performance by adding a percentage sign. Report the exact calculation and units, with missing inputs carried as unknown.
Rounding also matters. A displayed rate and total count do not reveal the exact underlying integer wins when the source policy or eligible population is unavailable. Ask for the originating ledger rather than back-solving an integer that looks plausible. A named outside review must have a subject and period; a founder record does not audit a subsequent chat stream.
Write the conclusion as a reconciliation
A useful result explains expected setups, represented setups, status counts, exclusions and any numerical totals that can be reproduced. If a marketing banner disagrees, retain both the banner and the declared calculation. A discrepancy may arise from a different period or definition; investigate before alleging intentional manipulation.
The free population tool performs only this declared status arithmetic. It does not ingest an archive or detect omitted losses. It returns an unknown conditional rate when no setups have resolved. Users can export the assumptions with the totals so a later reviewer can see the original denominator rather than inheriting an isolated percentage.
Completed fictional case
Twelve fictional originating setups resolve as five positive, three negative, one zero, one cancelled and two unresolved. Five of nine resolved outcomes are positive: 55.56% when rounded to two decimals. The status total remains twelve.
Five positive outcomes of +1 unit and three negative outcomes of -2 units sum to -1 unit before any further costs, despite the positive-outcome fraction exceeding half. No account capital is supplied, so this is not a percentage return. The cancellation and open cases remain in the inventory.
| Record | Represented finding | Boundary |
|---|---|---|
| Resolved denominator | 5 + 3 + 1 = 9 | Includes zero outcomes |
| Expected population | 9 + 1 + 2 = 12 | Cancelled and unresolved retained |
| Declared gross contribution | 5 x 1 - 3 x 2 = -1 unit | No account return inferred |
Primary sources and scope
Source inspection: 12 October 2026. Sources describe mechanisms or product categories, not the invented case outcomes. No paid channel, account or notification pipeline was connected for this edition.