Skip to short-horizon research
Short Term Trading StrategiesCondition / Request / Position

Cancel/replace records need unique event identities

Keep request lineage, cumulative status and actual execution fragments separate so a clean interface does not invent a flat position.

A plan can own several requests

Retain original plan ID and each order request's unique identity, with explicit replacement or cancellation relation. A changed instruction does not erase the earlier one. Request intention, acknowledgement and execution need separate sources. The publication has no actual broker order stream and no live cancel/replace algorithm. Its event specimen is an authored exercise showing why the identities matter. A public order-type reference explains a scoped mechanism but cannot witness a chosen account's full history, query retention or contemporaneous state.

A cancellation can coexist with execution

A cancellation request does not establish its result. Execution may occur while that request is pending; the actual selected service contract and original events settle the outcome. The paper journal declares two execution fragments before remainder cancellation is acknowledged. Already executed position quantity survives that acknowledgement. Nothing here submits an order or recommends a universal recovery action. A real operator needs authentic unique fills, remaining request and position records, together with authorised cloud ownership and native risk policy. An empty order view is not enough to certify flatness.

Cumulative notifications are not new fills

A repeated update can carry the same cumulative executed quantity. Do not sum those values as separate executions. Preserve the exact unique execution identity where available and declared query scope. The amount lens accepts only two manually entered fragments and does not deduplicate a live stream. Its completeness is a source question rather than an operational reconciliation receipt. An actual event history would additionally need version, timestamps, account and product identity. The eight authored rows produce no real latency, reliability rate, customer outcome or full historical population.

Keep amendments additive in exports

A corrected record should link the original field and reason rather than rewrite the earlier state as if it were always known. The original journal and workbench retain useful notes; their documented status is not account verification. Actual strategy research still needs frozen identity, one selected exit and independently checked master. Production reconciliation belongs in managed cloud services with durable evidence, not a local teaching script. No credential store, scheduler, workstation tunnel or fallback was added. The fictional quantities below remain a paper example, not a recovered funded position.

Fictional short-horizon evidence case

An authored ten-unit exit request has four declared units executed, then a cancel intention, then three more executed, then acknowledgement cancelling its remaining request. Total executed is seven, open position is three. A repeated cumulative-seven message would not add another seven. There is no actual account, timestamp, order or operational action.

ObjectRecordBounded finding
First execution4 declaredOpen six
Second execution3 declaredOpen three
Remainder cancelRequest scope onlyNot a closing fill
Invented closed price change, open mark, entry and fragment fees, and net snapshot
One invented position snapshot, not authentic account cash or a probability distribution.

Primary references and scope

Source review: 14 October 2026. Official mechanism descriptions are not this desk's paid-account test, independently captured fills or vendor-return audit.

Related short-horizon questions