Python has process starts and local ordering. The PLC acknowledgement carries only the reused job label.

Keep each source's order separately before aligning clocks, and look for independently identifiable shared events rather than using the disputed acknowledgement to prove its own place in the story.

Has the controller record owner checked for an independent request identifier or reception sequence?

They found no distinguishing identity in the retained records. Application attempts are separable; the acknowledgement remains unassigned.

That is a legitimate reconstruction result; keep the original files and the unassigned event while the maintainer defines distinct future attempt identities, without rewriting the old evidence as though it contained them.