Outstanding transactions hide latency — ordering rules determine whether the results are correct.
Outstanding = accepted work with an unfinished completion obligation at the named boundary.
Same ID ordered, different IDs may reorder — protocol and bridge dependent.
Publication and fences must satisfy the selected language/OS, architecture and device contracts.
Scoreboard and verification must model legal reorder, not assume strict order.
Ordering defines AXI ID rules, ACE barriers, PCIe relaxed ordering, and CPU memory models.
IDs are scoped to their interface and transaction direction; equal numbers can belong to independent ordering contexts.