Signal amendment and cancellation history
Preserve original versions, parent links and effective times without double-counting amendments as new calls.
Evidence methods, not a provider certification. Authored examples and user-entered check states are not independently verified trading results.
Original calls and versions are different counts
A signal can have several versions while remaining one original instruction. An archive that counts every amendment as a new call can inflate its denominator; an archive that overwrites originals can conceal what was initially known. Keep original_id, version_id, parent_version and effective-time fields separately. A human-readable amended badge is not enough to reconstruct the lineage.
The authored packet contains eight originals and two amendments, one linked to S001 and another to S004. Both point to a retained v1 parent. The ID checker reports amendment count without increasing the original count. It validates the declared parent graph as bookkeeping only. It does not authenticate the effective time, validate a signature or establish that a subscriber received the amended instruction.
A later version cannot borrow an earlier field claim
A change to stop, target, quantity or timing can alter the meaning of a trade instruction. Its new bytes deserve their own identity and evidence. An earlier commitment that omitted a target cannot establish that a later target was precommitted. The relation between versions may be clear while their economic execution remains unresolved. Record which fields changed and which earlier fields remain unchanged.
If an archive exports only the latest display, request the original attachment and earlier version history. Do not fabricate a plausible original from the final state. In the packet, amendment text is invented and no attestation is attached. The example demonstrates parent linkage, not a verified signal edit or evidence of misconduct. Actual message histories need genuine retained artifacts and a source-specific version policy.
Effective time needs its own chronology evidence
The claimed effective time of a revision is different from the time a file was downloaded for review. A reviewer needs to know when the new instruction became available under the purchased tier and whether any relevant execution occurred beforehand. A later favourable target cannot be applied retrospectively to a position without a declared causal execution convention.
The chronology tool can compare supplied UTC labels, but cannot prove publication or delivery. Treat amended-message existence, subscriber receipt, order acknowledgement and fill times as distinct events. Preserve uncertainty and out-of-order events rather than re-sorting everything to make the final narrative look consistent. Software sorting does not establish the causal order in which a trader could act.
Cancellation does not erase an executed position
A pre-fill cancellation and a post-fill exit instruction are different event chains. An archive must retain the outstanding order state, filled quantity and account evidence to determine which applies. Calling an already filled instruction cancelled can hide exposure or exclude an unfavourable outcome from a closed-only record. Yet missing records alone do not prove that this happened in any named service.
The packet's cancelled label explicitly means before any fill within the authored convention. No real broker event is supplied. The checker accepts terminal-state labels but does not infer them from prices or messages. A real review should join cancellations to the original order and account records, retaining partial fills and open quantities. Do not replace absent fills with a convenient assumption of zero exposure.
Report parent-chain exceptions separately
The orphan variant includes an amendment whose parent version is absent. The checker reports that relationship and withholds a reconciled amendment graph. Duplicate versions, unknown originals and cycles are also explicit exceptions. A parent that appears later in input order can still be valid if the graph is acyclic and complete; row order is not a substitute for version identity.
Preserve the problematic packet and a corrected packet as separate versions. A reviewer should not silently attach an orphan to a similar-looking instruction. The resulting exception register names the missing parent and requested source. It supports an actionable follow-up without fabricating a complete history, enlarging the original denominator or asserting that a syntactically valid chain proves chronological authenticity.
Mechanism and source references
Mechanism references are not provider certifications. The new editorial examples are authored exercises; no independent financial review was performed.
Inspect the working packet
Eight originals, four discrepancy variants and six chronology cases