BDS / Intraday usability

Intraday Signal Guides

Session-specific answers for reviewing what a subscriber could know and execute.

Edition: 12 October 2026. Desk research and labelled teaching scenarios.

Opening-Session Signals: Check the Information Available at the Decision

An opening price, auction event and continuous-session quote are different observations. Preserve the input the instruction actually used.

Separate the provider instruction from receipt, order state and account exposure. A delivered message is not a filled trade.

A planned exit condition, a provider close message and a subscriber fill are separate evidence objects.

Reconstruct only what the declared decision could know. A finished chart is not a record of delivered instructions.

A scanner match, news event, published trade and copied operation are different purchases, even when all arrive intraday.

Intraday evidence needs both an instruction population and an execution boundary. A large return headline does not supply either.

Fast delivery and a polished result card do not resolve an unclear instruction, account boundary or renewal.

Evaluate the work removed, the usable window and the full commitment. A favorable trial session is not proof of value or future gains.

Use a named venue session and absolute timestamps. A personal calendar day is not a universal trading day.

A message can remain readable after its condition expires. Evaluate the original rule instead of inheriting an old reference price.

Delay, absence and an unfilled order are different reasons an instruction may not become a subscriber trade.

Short reference distances make execution assumptions important. Compare them explicitly without inventing a net subscriber return.

A same-session promise needs an operating policy and evidence that the account reached the intended state.

An event time and a signal eligibility rule are separate inputs. Keep calendar changes and story corrections visible.

The planned quantity and the executed quantity can differ. Preserve the lifecycle rather than one success label.

Communication frequency is not the same as the eligible instruction population.

A subscription cannot replace understanding the instructed instrument, order and exit responsibility.

Testing the software mechanism, reconstructing a chart and observing an actual account are different experiments.

An advertised mechanism can be genuine while the selected plan does not fit the reader's account or clock.

Use explicit states for the whole observation population, not a showcase of closed winners.

A useful trial reflects the sessions you can actually monitor. It is not a strategy-validation sample.