Evaluation order lifecycles and holding permissions
Keep requested actions, accepted executions, remaining quantity and phase-specific holding conditions separate.
A timely request is not a completed execution
A reader can request a cancellation or close before a boundary while acceptance and execution occur later. Preserve request time, acknowledgement, filled quantity and remaining quantity as separate events. A successful click cannot establish the final account state.
The rule replay accepts supplied net account observations and does not infer an order path. It can compare a snapshot with an entered floor without proving how that snapshot was reached. A real evaluation question involving a deadline, session close or restricted interval needs the relevant order and account records, not an invented assumption that every request filled immediately.
Partial actions retain residual exposure
A partial close reduces quantity but can leave a position open. Cancelling an unfilled remainder of an entry order does not necessarily close the portion already filled. Keep outstanding order state and held quantity in separate inventories.
These distinctions are operational record questions, not a claim that every platform implements the same account structure. The hypothetical replay uses account-level balance and equity rather than reconstructing lots. A position ledger can explain residual exposure when the records exist. Linking the two requires stable original identities and compatible observation times rather than a shared symbol name alone.
Holding permission belongs to the phase
Overnight, weekend, event and session-close conditions can depend on the actual programme and account phase. Use the exact source terms and account agreement instead of a universal evaluation checklist. The linked FTMO holding FAQ illustrates why account context matters.
The new material supplies no blanket permission to use a particular signal source, hold a position or copy another account. Keep any rule about external signals or shared strategies with its source and version. A provider's historical result or a conviction label can remain useful background without becoming the programme's authorisation for the intended account route.
Do not rewrite a native exit to fit a later goal
The strategy's original exit policy and an external evaluation constraint are different contracts. If the selected system uses minute-based execution, a completed-session report must not silently become a daily stop manager. Preserve whole-position intent, native risk and maximum-hold rules unless a change is separately authorised.
An account may be unsuitable for the intended workflow under its actual terms. That is a compatibility question, not a reason to manufacture a different historical strategy. The teaching tools have no execution API and issue no close commands. They can help identify a conflict while leaving the real trading policy and account decision outside their scope.
Keep uncertainty at the deadline
A record rounded to a minute or second may not establish which event preceded a boundary within that interval. Save source precision and clock mapping. Do not invent milliseconds or reorder events to obtain an apparent timely exit.
The replay deliberately requires strictly increasing entered UTC snapshot times so its sequence is unambiguous. That validation is not authentication of a real request or fill. If authentic events have uncertain order, retain an unresolved join and the applicable source clarification. A valid browser calculation should not be used to erase the uncertainty that the underlying account records actually contain.
A lifecycle memo for an evaluation review
Record original instruction, requested action, account event, remaining quantity, applicable phase permission and the boundary observation. State which values are actual records and which are scenarios. Keep adverse and unresolved examples in the same observation population.
The new packet has no genuine orders or participant outcomes. It illustrates account-state comparisons under supplied observations, while the daily ledger illustrates closed-result arithmetic. Neither establishes a pass or payout. A useful review identifies the missing operational relationship and its source rather than replace it with a broad assurance that the workflow is always compatible.
Reference documents
These references cover mechanisms and source definitions. The worked numbers on this page are invented teaching inputs, not provider or account records.