Joint gap risk and shared exposure
Compare planned stop loss with disclosed hypothetical account shocks without pretending to estimate correlation, tail probability or a guaranteed maximum.
Specify the stop rule, trigger mechanism and amendment history, then test gaps and partial fills without promising a maximum loss.
Educational risk arithmetic, not personal sizing advice. Stops do not guarantee fills. Stress inputs are invented assumptions without assigned probabilities; margin, shorts and derivatives need their own contracts.
A strategy's exit rule can specify a price condition, elapsed holding clock or another observable event. An order instruction specifies how a broker should act. These layers need not be identical: a software rule can generate a market instruction after a condition becomes observable, while a broker-held stop has its own trigger mechanism. Name both layers instead of calling everything a stop-loss price.
Record the instrument, price source, eligible session and data availability. A rule evaluated on completed bars has different timing from one evaluated on minute events or executable quotes. Preserve the native research and execution policy rather than silently changing the observation frequency. A completed-session routine may update a holding clock without gaining authority to introduce daily profit floors or daily stop exits. The correct contract depends on the named system, not on a generic article's convenient chart interval.
Investor.gov explains that a stop order becomes a market order when its trigger price is reached; it distinguishes this from a limit condition. A stop trigger is therefore not proof of the eventual price. A price-constrained instruction can have a different non-execution risk. Check the actual broker's terms, trigger source, supported sessions and order validity before describing any specific mechanism as available.
Do not infer a guaranteed fill from a candle crossing the level. A bar's high and low may not identify event order, usable quantity or a price available after the instruction arrived. Save execution reports when discussing actual trades, and label hypothetical conventions when studying history. This guide does not choose an order type for a reader or certify a broker. It provides the fields needed to compare an intended exit with the mechanism that would attempt it.
Use invented fifty-share long exposure entered at 100, a planned stop at 98 and additional round-trip cost 0.10 per share. If the assumed fill is 98, loss is fifty times (2+0.10), or 105. If the hypothetical execution instead occurs at 94, loss is fifty times (6+0.10), or 305. The quantity has not changed; the execution assumption has.
These are two accounting scenarios, not probabilities or observed slippage. The extra cost must not already be included in the prices. An exit at zero would be another scenario with its own interpretation, not evidence that every gap reaches zero. Keep the underlying currency, unit quantity and source convention attached to the result. Use the site's joint-gap worksheet only within its cash-funded whole-long-share lane; it does not model short obligations, derivative multipliers or broker-specific guaranteed-stop products.
Specify whether the stop is fixed, adjusted by a named causal rule or changed by an authorised intervention. Record each revision with its effective time, reason and previous value. A changed chart level is not necessarily a changed broker order. Preserve submission and acknowledgement state, particularly when an amendment races with an execution. A whole-position exit must not become a partial-exit policy silently.
For research, choose one predeclared exit in the experiment and keep entry ranking based on the original entry objective. Later exit results can validate or reject the implementation without selecting a new entry retroactively. An exit tournament after seeing reserved outcomes reuses that information. If a policy genuinely changes, retain the earlier record and evaluate the new version under an appropriate fresh boundary. Do not report a revised exit history as if every original instruction had remained unchanged.
A maximum hold can be expressed in observations, completed sessions or elapsed time; those clocks behave differently across breaks and missing data. Name the start event and advancement rule. A skipped observation should not silently extend or shorten the policy unless that behaviour is explicit. A missing trigger price requires a documented state rather than an invented no-exit result.
An estimated reference half-life does not authorise extending a losing position. Nor does a target touched before a stop in a favourable reconstruction prove the actual event sequence when the source only supplies a bar range. Preserve ambiguity and use a predeclared, clearly labelled hypothetical convention where the evidence cannot resolve it. Software tests should cover missing data, equal-to-threshold observations, amendments and maximum hold. Their passing outcomes check policy implementation, not market profitability.
The position record needs entry quantity, funding, existing exposure, intended exit and the remaining order state after every execution. A correctly triggered stop on one position cannot establish total account control. Multiple instructions may share one risk event, and partial fills can leave unexpected residual exposure. Reconcile the actual account rather than assuming a submitted exit has already removed the position.
Use the blank stop-policy record to specify these details before accepting a provider's defined-stop claim. Compare planned loss with explicitly labelled execution scenarios and retain unanswered broker-mechanism questions. There is no universal stop distance or suitable risk percentage asserted here. A consumer can reasonably conclude that an exit is well specified while execution evidence remains incomplete. That layered conclusion is more precise than a blanket claim that every trade has a guaranteed loss ceiling.
| Object | Preserve | Do not infer |
|---|---|---|
| Rule | Source, frequency and holding clock | Every bar crossing is an executable exit |
| Mechanism | Trigger, order and fill separately | A stop price guarantees the loss ceiling |
| Revision | Authority, acknowledgement and prior version | A later rescue preserves the original policy |
Download blank review record (CSV)
Headers only. No trades, subscriber outcomes or operating receipts are supplied.
Documentation establishes the stated mechanism, not tested trading performance. Checked 10 October 2026; a later version can differ.
Compare planned stop loss with disclosed hypothetical account shocks without pretending to estimate correlation, tail probability or a guaranteed maximum.
Keep account currency, position increments, original risk, recovery percentages and deposits separate before drawing conclusions from a risk statistic.
Turn a risk formula into a versioned policy with ownership, funding checks, monitoring, exceptions and durable cloud evidence.
The original protocol's sections and checkpoints remain. The new specimen is not an alternative exit-policy tournament; it compares terminal liquidation assumptions while holding a reference stop and positions fixed. It does not tell a reader where to move a stop or how to alter a production model's manager. A completed-session clock is not daily stop ownership. A real instruction and native minute execution policy need their original identities preserved before any reproduction or account finding is made.
The fictional three-position case has a 220 joint planned reference and a 650 assumed joint gap loss. Those are cash results under the specified hypothetical full exits and costs, not quotes that a broker could promise. A stop-limit condition can create a different execution question than a market trigger, so the actual order contract remains relevant. This exercise supplies neither order placement nor a personal maximum-loss guarantee, and its exact arithmetic should not be presented as a tested live exit.