BTA / Delivery desk
Instruction Versioning and Amendment Authority
Keep the first instruction and every known change connected.
Stable family
Separate original ID, version and transport attempt ID. Ticker similarity is not enough to decide whether two objects are one instruction.
Effective update
An amendment needs changed fields, effective meaning and responsible authority. Arrival order alone cannot determine which source version governs.
Account boundary
A publisher update is not automatically an order modification. Account permission, request and acknowledgement need separate evidence.
Record the Claim Boundary
Name the precise artifact and separate documented, attributed, hypothetical and unresolved evidence. These criteria do not assign a star score or certify a provider.
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.