BDS / Intraday usability
Audit the Original Day-Trading Exit Rule, Not the Best Later Price
A planned exit condition, a provider close message and a subscriber fill are separate evidence objects.
Identify the exit owner
Ask whether the service supplies a complete exit rule, a later discretionary update or only an entry idea. A same-session label does not explain who handles expiry, partial exits or failed closes. Those responsibilities determine the product being compared.
Keep the original rule with its version and publication record. A later refinement can be legitimate, but it must not retroactively replace the rule used for an earlier observation.
Preserve the intended order behavior
An intended stop is not a guarantee of the final execution price. Check the relevant official order definitions and the actual broker/product terms. A limit condition and a market-triggering condition have different execution boundaries.
The publication does not choose an exit for the reader or change any production model policy. This is an evidence review: what instruction existed, what action was attempted and what record supports the result?
Resolve partial and conflicting updates
An instruction to reduce part of a position needs a quantity or a defined fraction, plus the treatment of the remainder. Preserve every amendment and cancellation. If two updates conflict, note the authoritative policy or leave the interpretation unresolved.
Do not treat several targets as permission to choose whichever later looks best. The scoring rule should be known before the outcome, including how costs and remaining exposure are handled.
Worked intrabar ambiguity
Hypothetical example: one price bar contains both the intended target and stop after a possible entry. The summary high and low do not reveal the required sequence. Under that data resolution, an outcome may remain ambiguous.
Finer observations can help establish order, but still need their own availability and fill convention. A retrospective price path is not automatically proof that a subscriber obtained either displayed price.
Keep failed exits at the session boundary
A closing request can be rejected, remain unfilled or close only part of the position. The ledger should preserve the order state and remaining exposure rather than declaring the account finished because the publisher used the word closed.
For copying, inspect the actual follower policy rather than inferring it from the source account. The account and subscription cancellation processes are different questions.
Publish the supported scope
A review can conclude that the original rule is documented while execution remains untested. A hypothetical replay should carry its assumptions. An actual account conclusion requires the relevant order and position records.
No exit tournament or model research is performed by this guide. It does not rank entry models using exit-adjusted results, replace a research fill convention or recommend an account action.
Do not reopen the method to favor a result
Once the exit interpretation is declared, preserve it through the observation. A different exit can be examined in a separately labelled exercise, but it should not retroactively decide which original calls were successful. The site does not select production exits, conduct a model tournament or turn exit-adjusted outcomes into an entry-ranking objective.
A multiple-target evidence packet
Request the original quantities or fractions, priority rules, amendment policy and treatment of the remaining position. A list of price levels alone does not settle the account path. If the rule is absent, the outcome stays unresolved rather than becoming a favorable average chosen after the fact.
Distinguish instructions from reconciliation
A provider can issue a clear close instruction without supplying the follower's confirmation. Preserve the instruction as documented while leaving the account state unverified. A subscriber close record should link actual operations and remaining quantities. This prevents an understandable message from being overstated as completed execution.
Evidence Packet
| Evidence object | Record to retain |
|---|---|
| Original exit | Rule, version and responsible party |
| Sequence uncertainty | Resolution and ambiguity policy |
| Remaining position | Partial, failed and unresolved close events |
Related Session Questions
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.