Maximum Drawdown and Moving Floors
An advertised loss percentage is incomplete without a reference and monitoring clock.
Static and Trailing References
Identify whether the floor stays fixed or follows a stated high-water reference. Then establish when that reference updates. End-of-day reference updates do not necessarily mean breaches are observed only at the close.
Costs and Floating P&L
Record which components enter monitored equity and whether touching the boundary fails. A closing balance can conceal an earlier intraday breach. Generic examples must not override authoritative account state.
Primary Sources
An entered loss rule needs six fields
Record starting reference, qualifying measure, update clock, monitored measure, cap if any and boundary operator. Add cost convention and account identity beside those mechanics. A loss percentage without them can describe incompatible policies. The replay exposes these fields instead of choosing a rule from a brand name.
Work a path rather than only a final balance
The invented packet reaches equity 108,000 while balance is 100,000, then records equity 96,000 before a profitable close. An intraday-equity peak and a balance peak differ. The reference choice therefore changes whether the intermediate observation sits below an entered floor. All rows and exception IDs are retained; a recovered final snapshot is not a rollback of history.
Keep observed and subsequent floors apart
End-session mode compares the close with the active reference, then qualifies its closing balance for the next observation. The final case has observed floor 94,000 and subsequent floor 96,000. Both are correct under that explicitly entered operation order. A real programme needs its actual effective time rather than this generic after-close convention.
Coverage and compatibility remain separate
The worksheet checks supplied snapshots only. Missing equity is rejected, external flows are unmodelled and continuous monitoring remains null. A source-compatible calculation still does not authorise holding, copying or strategy changes. Keep the native minute policy and actual account permission unchanged while investigating whether the evaluation fits the intended workflow.
An exact boundary with a carried loss
Use the invented session-B opening balance 104,000 and daily amount 5,000. Its floor is 99,000 while supplied equity is also 99,000. A touch-inclusive exception convention and a strict-below convention differ at this same point. Preserve source operator and precision before attaching either finding to a real account. A rounded dashboard alone may not provide exact internal equality.
The later 106,000 close does not erase a retained earlier exception in the supplied history. A genuine programme can have its own review and account process, which the calculator does not model. The teaching result therefore concerns the original observation and entered policy, not an automatic actual account termination or successful appeal. Keep the historical event and any subsequent administrative decision as different records.
An exception and an unobserved interval
A snapshot replay can identify a supplied state outside an entered boundary while leaving intervening states unknown. Conversely, rows above a floor do not establish continuous compliance. Save the coverage interval, source precision and original population rather than describe a selected final screenshot as the complete path.
For the new packet, continuous monitoring remains null and missing equity is rejected. No market-frequency inference, probability estimate or optimal headroom buffer follows from its fictional cases. A live operational claim would need authoritative account data, current deployed cloud ownership and durable evidence beyond local practice. The replay supplies none of that service. It adds value as a bounded interpretation record while preserving the actual programme terms and the selected strategy's native policy.