BDS / Intraday usability
Complete Intraday History: Keep Amendments, Cancellations and Gaps
The lifecycle is the evidence object, not only the final result card.
Original identity
Retain the first instruction and a stable setup identifier where available. Link channels and repeated messages rather than assuming every notification is a new trade.
Revision chain
Archive changes with their times and original relationship. A legitimate amendment still cannot erase what was known at the earlier decision.
Failure population
Keep expired, missed, unsupported and unresolved objects. They matter to usability even when no account operation exists. Declare their treatment before totals are reported.
No invented reconstruction
If a deleted object cannot be retrieved, preserve that gap. Neither a later chart nor a testimonial can supply the missing original. Narrow the claim instead of filling the row favorably.
Apply the Criterion
Write the exact missing artifact and whether the claim is documented, attributed, hypothetical or unresolved. A completed field is not a certification, and the criterion does not assign a star score.
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.