BDS / Intraday usability
Intraday Timestamps: Commitments Are Not Receipt or Fill Records
Inspect exact bytes and attestation state before extending a timestamp claim.
What was committed?
Obtain the exact preimage, encoding and original values. A field absent from the commitment is not authenticated by its receipt. An appended exit or outcome needs its own supporting record.
When was it attested?
Distinguish pending submission from a verified attestation and retain the attestation time. A confirmed commitment concerns its covered bytes; it is not a subscriber-delivery or broker-execution record.
What is the intraday timing gap?
Publication, receipt, review and order events are separate clocks. A timestamp can help examine whether specified data existed by a time without showing how promptly a buyer could act.
What conclusion is supported?
A documented commitment mechanism can coexist with unresolved execution. It does not certify profitability, instrument compatibility or stop/target fields that were never included.
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.