01
the benchmark used to judge execution — Measurement contract
Define one observation and decide whether cost is recognized at order, fill, exit, statement, or another event. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
02
the benchmark used to judge execution — Unit ledger
State price unit, contract quantity, P&L currency, account currency, and one-way or round-trip scope in separate fields. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
03
the benchmark used to judge execution — Timestamp alignment
Place order, fill, conversion, and charging events on one explicit clock rather than relying on a quoted schedule time. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
04
the benchmark used to judge execution — Baseline scenario
Store gross profit, total cost, net profit, and break-even under the conditions regarded as ordinary. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
05
the benchmark used to judge execution — Conservative scenario
Replace central inputs with adverse but plausible quantiles, quote sides, and extra charges. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
06
the benchmark used to judge execution — Stress scenario
Calculate low-frequency boundaries such as holidays, discontinuities, specification changes, and liquidity shocks separately. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
07
the benchmark used to judge execution — Missing data and corrections
Do not turn unknown values into zero; retain an unresolved state and replace it when a statement or correction arrives. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
08
the benchmark used to judge execution — Statement reconciliation
Decompose model-to-statement differences into rate, base amount, event count, rounding, and timestamp effects. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
09
the benchmark used to judge execution — Version retention
Save fee schedules, contract specifications, calendars, conversion rules, and equations with effective dates. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.
10
the benchmark used to judge execution — Decision record
Record which input changed the conclusion and what action followed, with a concise economic reason. For the benchmark used to judge execution, bind the boundary “Recompute signed shortfall with a direction-consistent benchmark and require the execution ranking and net-P&L conclusion to survive legitimate benchmark choices.” to the required evidence “Synchronized bid, ask, mid and last prices; order-send, receipt and fill timestamps; direction and order type; preserve clock granularity and tolerance.”.