Skip to content

BDS / Intraday usability

Day-Signal Session Workbench and Journal

Compare explicit UTC timing and hypothetical costs, then keep the complete observation and product-evidence record.

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

Hypothetical Timing and Cost Scenario

No live feed or broker is connected. The entered times and prices are invented teaching assumptions, not measured provider data.

Entered scenario

Timing and reference distances use the visible assumptions.

Hypothetical scenario conventions
AssumptionBoundary
Time inputsExplicit UTC instants; selected zone changes display only.
Entry deadlineInclusive expiry; review must be before the exclusive session close.
CalendarUser-supplied session, not a live venue/holiday lookup.
Price arithmeticFixed original stop/target and assumed adverse entry movement; no actual fill.
Additional costOnly the round-trip component not already embedded in the prices.

Blank Session Observation Journal

Keep eligible, missed, cancelled and unresolved objects. Eligible is not an execution confirmation. Entries are unverified reader notes.

Synthetic example, not real alerts

0 reader states recorded

Original setup 1

Original setup 2

Original setup 3

Original setup 4

Journal definitions and evidence classes

Product Evidence Record

These ten states organize references, not a provider score or completed independent audit.

0 documented10 unresolved0 not applicable

RECORD 01

Session boundary

Which venue session and timezone define the trading day? A calendar midnight elsewhere cannot silently determine an intraday service exit.

Evidence: Session calendar and timezone

RECORD 02

Opening conditions

What eligible data exists near the opening transition? A chart replay may hide delayed quotes, auctions or observations unavailable to the subscriber.

Evidence: Data availability at session open

RECORD 03

Instruction horizon

How long does an entry remain actionable? A fast setup and a later commentary update must not inherit the same hypothetical fill.

Evidence: Instruction expiry and entry condition

RECORD 04

Receipt latency

Which actual times connect publication and subscriber receipt? A server timestamp alone cannot establish a usable intraday decision window.

Evidence: Published and received timestamps

RECORD 05

Quantity rounding

Does the proposed size respect the selected account and product increments? A nominal allocation can become a different exposure after rounding.

Evidence: Units, multiplier and permitted increment

RECORD 06

Adverse execution

Which spread and unavailable-price assumptions belong to the research? A planned stop is not proof that an exit occurred at that price.

Evidence: Fill basis and execution exceptions

RECORD 07

Duplicate triggers

Can several notifications represent one underlying setup? Distinguish message frequency from the eligible call population before counting trades.

Evidence: Setup ID and related messages

RECORD 08

Concurrent positions

What exposure remains when another intraday call arrives? Separate instruction-level performance from the marked account with overlapping decisions.

Evidence: Joint positions at each decision

RECORD 09

Session close

Who owns positions that remain open after the declared day? A same-session label needs an actual close policy and a record of failed exits.

Evidence: Closing instruction and remaining exposure

RECORD 10

Service conclusion

Which coverage and execution defects remain unresolved? Intraday density does not itself establish accuracy, suitability or a verified account result.

Evidence: Supported service assessment

Entries remain in the open page until export or clearing. They are not submitted or stored in local storage. Do not enter account credentials.

Primary References

The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.