BTA / Delivery desk
Trading Alert Amendments: Keep the First Version
An update needs a relationship, authority and effective boundary, not just a newer-looking message.
What changed and when?
A change to direction, entry, validity or an exit should identify the affected original instruction. Retain changed fields and unchanged fields distinctly. A replacement message that omits part of the original can be ambiguous: is the omitted field inherited or removed? Request the actual amendment convention rather than supplying the convenient interpretation.
Preserve the first version and the circumstances under which it was observed. Overwriting it with a final summary erases the reader's decision context. A retrospective history should show the complete version chain, including withdrawals and corrections. The presence of an update does not prove it reached every destination before an account action.
Identify the responsible authority
An editorial source may be authorised to change its own instruction without controlling an existing broker order. A connector may need another permission to act on that amendment. Record who owns each transition. A new target in a chat message is not automatically an accepted order modification.
Keep the update's effective boundary, dispatch, receipt and any acknowledgement where available. These fields need their own provenance. If the original was already expired or cancelled, the meaning of another update must be documented. Do not infer that a fresh receipt revives the old instruction's entry window.
Review the entire instruction family
For a documentary comparison, ask for an example that includes an original, amendment and final disposition. For a safely isolated route test, create clearly labelled synthetic versions and declare how they should be interpreted. Neither exercise establishes actual trading performance or proves complete historical delivery.
The workbench retains version information as reader-entered notes, not an authenticated source registry. A useful conclusion describes the inspected chain and names any missing authority or effective-time record. It does not quietly replace an unresolved first version with the final profitable-looking one.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Change set | Affected original and changed field list |
| Authority | Source instruction versus order modification |
| Version chain | Original, amendments and final disposition |
Continue the Investigation
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.