Educational Simulation Archive
S&P 500 Support Breach Analysis
Simulation Lab

S&P 500 Support Breach Analysis

Examining hypothetical order flow dislocations and synthetic support failure events within a controlled mock trading ledger.

Strictly educational archive. Simulated analysis and hypothetical models only.
SIMULATED HYPOTHETICAL
Marcus Thorne 2026-11-16
S&P 500 Support Breach Analysis

Scenario Overview

This analysis reconstructs a synthetic support failure: a widely watched level on a fictional index basket (DEMO-index) is breached on heavy simulated volume, and the journal's task is to document the event as a sequence of decisions rather than as a story about the level itself.

Levels are magnets for hindsight. After a breach, 'everyone saw it coming.' The scenario was designed to counter exactly that: the participant logged their expectation and planned response before the replay was allowed to cross the level.

All prints, order-flow readouts, and depth snapshots are replay-engine output. The real index that inspired the scenario is never referenced by ticker — the lesson travels, the symbol does not matter.

Hypothesis Log — Pre-Breach

FieldWritten Before BreachReview Question
Watched levelSynthetic round-number support on DEMO-indexWas the level defined by a rule or drawn by eye?
Participant expectation'If breached with volume, continuation for 2 sessions'Was the expectation falsifiable?
Planned responseNo simulated entry; observe and log onlyWas 'do nothing' treated as a plan?
InvalidationBreach fails to hold for one synthetic closeCould the plan be proven wrong in one session?
Data to capturePrint rate, synthetic volume ratio, depth at levelWas capture defined before the event?
Pre-committed fields from the Reviewbook — the artifact under review.

Simulated Observations

  • Synthetic volume expanded to roughly 2.4× the replay's session baseline in the hour surrounding the breach — the participant's written expectation had anticipated expansion.
  • Depth at the level, as rendered by the engine, evaporated within two synthetic ticks of the first sub-level print; the log notes the simulator cannot show which real orders would have pulled versus held.
  • A secondary 'retest' move returned to the level within the session — the journal's value is that the plan had already specified what a retest would and would not mean.
  • Three hypothetical resting orders placed at the level by the sandbox's scenario script displayed as filled instantly; the log flags that real orders would have faced queue uncertainty the engine omits.

Interpreting the Breach

The scenario separates three things a live market fuses together: the event (the level failed), the mechanism (modeled volume overwhelmed modeled depth), and the meaning (nothing, without a pre-written frame).

Because the expectation was written in advance, the review could ask a clean question: did the session confirm, refute, or leave open the participant's stated mechanism? In this log, the volume pattern matched the stated expectation — which is recorded as 'one favorable observation in a synthetic regime,' not as validation.

This is the core Reviewbook discipline applied to market folklore: a level, a breach, and a retest are inputs for a journal entry, not evidence for a trading theory.

Methodology and Limits

The replay renders support failure mechanically: scripted volume expansion meets a depth book that decays on a schedule. It cannot reproduce the strategic interaction of real participants — large holders defending a level, algos hunting stops beneath it, or the self-fulfilling component of widely watched prices.

Accordingly, the study treats the breach as a documentation drill. Any claim about 'what levels do' in real markets is out of scope — and is flagged as such inside the log itself.

Review Checklist

  • Was the level defined by a stated rule before the replay, or rationalized after the prints?
  • Did the log distinguish 'order displayed as filled' from 'a real order would have been filled'?
  • Was the retest interpreted using only pre-written plan language?
  • Does the entry avoid any claim that this scenario predicts real level behavior?

Review Takeaways

The exercise demonstrates the Reviewbook's central swap: instead of asking 'did the level work?', the review asks 'did the participant work the plan?' The first question is unanswerable in a sandbox; the second is fully auditable.

Replaying famous-feeling market moments is valuable precisely because the participant already 'knows the ending' — which makes it the hardest possible environment for honest, timestamped expectation logging, and therefore excellent training.

Frequently Asked Questions

No. The level, the volume expansion, and the retest are replay-engine scripts. Real index names appear only as genre shorthand — no claim is made about how real support levels behave.

Because 'do nothing' is a decision too, and the exercise tests whether participants can pre-commit to inaction. A plan that only covers entries leaves the most common real-world response undocumented.

A rule produces the same level for any reader: 'synthetic round number touched twice with rejection closes' is a rule; 'the obvious support' is an opinion. Only the first can be journaled and reviewed.

It builds skill at documenting levels — expectation writing, timestamped logging, plan adherence. Whether those documents transfer to live level-trading is exactly what this study cannot claim.

Review Note

Replayed breaches are best used to rehearse documentation speed and plan adherence — not to build confidence in level-trading outcomes.

Continue Exploring

Simulation Lab

Anthropic IPO Market Impact

Simulating market depth shifts, capitalization reallocation, and foundational AI peer valuation revisions under hypothetical listing conditions.