Skip to content

BTA / Delivery desk

Trading Alert Delivery Workbench

Keep explicit UTC observations, clock-bound intervals, instruction-family events and a ten-question evidence record.

12 October 2026 / public documents and labelled test designs

Dispatch, Receipt and Observed-Action Timeline

Enter explicit UTC observations and justified clock bounds. No external clock, live receiver or account is connected. Unknown values stay empty.

Dispatch
Destination receipt
Observed action, optional

Each interval expands the apparent difference by both entered absolute bounds. Overlap with zero does not establish event order. Entirely negative bounds conflict with the declared sequence. Observed action is not assumed to be a broker fill.

Clock assumptions and interval method

Blank Instruction-Family Event Ledger

Retain retries, changes, withdrawals and unknown events. These entries are unverified reader notes, not collected vendor data.

Invented test kitBlank protocol

0 reader events recorded

Event 1
Event 2
Event 3
Event 4
Event 5
Event 6

Delivery Evidence Record

Ten questions for the selected route; recorded answers are not authenticated by BTA.

0 documented10 unresolved0 not applicable

RECORD 01

Trigger definition

What exact condition causes the alert? Preserve indicator inputs and completed-versus-forming observation rules instead of inferring them from a later chart.

Evidence: Condition and input version

RECORD 02

Creation snapshot

Which settings existed when the alert instance was created? A current chart configuration may not describe the older running alert.

Evidence: Saved instance configuration

RECORD 03

Data availability

When did the underlying observation become usable? Source time, platform processing and revised data can differ from the displayed bar label.

Evidence: Observation and availability times

RECORD 04

Trigger identity

Can every firing be identified uniquely? Retries and duplicated messages should not silently become additional independent trading calls.

Evidence: Trigger ID and retry relation

RECORD 05

Delivery destination

Which endpoint or channel received the message? An acknowledged webhook and an end-user notification establish different points in the delivery chain.

Evidence: Endpoint and receipt record

RECORD 06

Late-message policy

What makes a delivered instruction too old for the stated rule? A later favorable price does not restore the decision opportunity that was missed.

Evidence: Validity window and stale status

RECORD 07

Payload completeness

Does the delivered message retain direction, instrument and intended action? Truncation or a changed template can leave a trigger impossible to interpret.

Evidence: Original and received payload

RECORD 08

Downstream order

Which separate order followed the message, if any? A successful alert transport does not prove an executable account instruction or broker fill.

Evidence: Order reference or no-order status

RECORD 09

Failure evidence

Where are timeout, rejection and unavailable events retained? An investigation that keeps only successful deliveries cannot describe coverage or reliability.

Evidence: Failure log and missing intervals

RECORD 10

Bounded finding

Which stage was actually tested? State a transport or configuration result without turning it into measured strategy profitability.

Evidence: Stage-specific conclusion

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

Source Boundaries

Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.