Aspen Analytics
The SPY Framework: A User’s Guide
This page tells you what the bi-weekly SPY Framework posts are, what each issue contains, and how to use them over time.
What These Posts Are
Most market commentary tells you what just happened.
The bi-weekly SPY Framework posts do something different. Each issue commits to a regime read — what the market is structurally doing right now — names the specific conditions that would change that read, and time-stamps the commitment.
Two weeks later, the next issue marks the previous read against where the market actually went.
The structure is the whole point. Anyone can call a regime in hindsight. Calling it in advance, naming what would change the call, and publishing the audit two weeks later is a different practice.
Why SPY
SPY is the locomotive. Everything else is a car on the train. It does not matter whether you trade SPY directly, individual equities, sector ETFs, or swing positions held overnight — the locomotive sets the direction, the speed, and the conditions under which your trade either works or grinds against you.
Reading SPY structurally is the read that drives the read on everything else.
Where These Posts Come From
These are not written on Sunday night by reviewing the prior two weeks in retrospect.
Each issue is built on top of real-time market reads recorded during the trading day. When the tape is doing something worth capturing — a developing regime tell, an input shift, a level holding or breaking on confluence — the recorder goes on and the read gets spoken aloud while it’s still forming. Some of those reads lead to trades. Most do not. The point of capturing them isn’t the trades. The point is the read itself, preserved in the moment it was made, not reconstructed after the fact.
What makes the bi-weekly possible is not any single observation. It is the layering of observations across sessions. Each recorded read is a snapshot — a slice of the tape, a state of the inputs, a posture of the framework. The insight comes from stacking the snapshots and looking across them. Patterns reveal themselves because they appear in layer after layer. Regime tension becomes visible because a recent layer disagrees with the ones beneath it. The synthesis in any bi-weekly post is built from this stack, not from any individual session.
The advantage of real-time capture is what it preserves. After-the-fact commentary loses whatever wasn’t memorable enough to be retained — and most of what matters in a developing regime is exactly the kind of detail that gets lost in retrospective review. Real-time capture only loses what wasn’t worth recording in the first place. The losses are smaller, earlier, and more controllable.
The closest analogy is a book being written in real time. Each session is a chapter. The recurring themes carry across — what the framework is watching, where the regime is intact, where stress is accumulating — and the chapters compound into a coherent record. Some sessions confirm what came before. Some break the pattern and reset the read.
By the time a bi-weekly post publishes, the regime call inside it has been forming across roughly ten sessions of live observation. The post is the synthesis. The substrate is the daily work.
This matters because the alternative — writing regime calls in retrospect — is the most common form of commentary, and the form most likely to look prescient by accident. Real-time observation cannot be backdated. The audit trail is what makes that distinction visible.
What Each Issue Contains
Every bi-weekly post is built from the same four elements:
A regime read. The structural signature of what the market is doing right now — mean-reverting, contested two-way, trending with conviction, or transitioning between regimes. Stated plainly, not hedged.
The tension worth naming. Whatever is developing under the regime that may or may not become a turn. Intact regimes still produce stress, and the stress is worth tracking even when the read remains unchanged.
Tripwires. Specific, named conditions that would force a revision of the regime read. The tripwires are auditable two weeks later — they either tripped or they did not.
A confidence statement and a forward question. What I am confident in, what I am not, and the binary question whose resolution will set the tone for the next issue.
The structure is identical issue to issue. The content shifts with the tape. The audit trail accumulates.
How to Use These Posts
The bi-weekly is not a trade signal service. It will not tell you what to buy Tuesday at 10:15.
What it will tell you is what posture to be in. Patient or aggressive. Defensive or opportunistic. Fading strength or buying weakness. The posture sets the conditions under which any particular trade — yours or mine — is taken, sized, or refused.
Read the bi-weekly to know the regime. Trade your own framework against that regime, or stay on the sidelines if the regime does not pay your style.
What Comes Next
The bi-weekly demonstrates the read. The Aspen Discretionary Service is what the read produces in trade form — specific SPY, equity & ETF setups that align with the regime the bi-weekly is monitoring, taken with sizing and timing informed by the same structural framework that produces these posts.
The bi-weekly is free. The audit trail is public.
If the regime reads land where the tape actually goes, issue after issue, tripwire after tripwire — the service does the rest of the work.
If they do not, you will see that too.
That is the trade.
