Case 01Clean order lifecycle
Synthetic · expected path
New → ACK → partial fills → fill
The report reconstructs one clean timeline from the new order, ACK, partial fills, and final fill.
Synthetic report gallery
Open a report before you install.
Five synthetic scenarios show the current HTML report. They cover clean reconstruction, supported anomalies, and status-request behavior.
Five synthetic scenarios
Review each lifecycle and its FIX messages.
Each published scenario will include an HTML report, packed JSON, and the exact synthetic input FIX log. All controls are disabled in this proof.
Every example provides: HTML report · Packed JSON · Input FIX log
Case 02Stop-limit activation anomaly
Synthetic · anomaly present
Fill before activation
The report shows the supported fill_before_activation anomaly. View event jumps to the fill before the activation restatement.
Case 03Cancel/replace linkage anomaly
Synthetic · anomaly present
Invalid OrigClOrdID reference
The cancel/replace flow references an unknown or unrecognized OrigClOrdID. The report shows the broken order lineage.
Case 04Status request edge
Synthetic · separate timeline
Unknown-order status request
A status request for an unknown order stays separate from the live order timeline.
Case 05Status request response
Synthetic · informational
Nothing Done remains informational
The Nothing Done status response remains informational in the order timeline.
Questions for report review
Questions for report review
Feedback and support destinations are not active in this copy-review proof.
- 01
Did the report reconstruct the expected order lifecycle?
- 02
Was any anomaly wrong, unclear, or misleading?
- 03
Could you share the HTML report through an approved channel?
- 04
Was any important summary or evidence missing?
Data safety