Tape reading constrains behavior — aggressive prints that hold, VWAP acceptance, spread gates, index agreement. If it cannot be audited on Sunday, it was a guess with better vocabulary.
## Rails that stay on the sheet
- Stack for decisions, not decoration.
- Disagreement reduces size or skips.
- Invalidation written in cents or an auditable structure break before entry.
## Framework I will not skip
1. Write the definition before the open (level, trigger, invalidation in cents, size, max loss). Verbal plans do not count.
2. Liquidity and spread gates beat narrative. If live spread exceeds max, observe or cut — the chart can still "look perfect."
3. One clean attempt per idea in a window. Failed attempt means new structure, not revenge.
4. SPY/QQQ context for single-name full size; cut or skip when the basket disagrees.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.
## Worked example — Level soup entry
Prior day H/L + VWAP + OR all drawn; entry anywhere 'near confluence.' Stacking requires agreement rules: which level is invalidation, which is target, what disagreement means for size.
I keep examples in cents and clock time so Sunday review can tag the behavior — not rewrite it as a mood.
## Failure modes
- Ignoring the rails above on **Level stacking: prior day H/L + VWAP + opening range** and substituting confidence.
- Adding size after adverse selection because the story still feels right.
- Paying open microstructure tax that midday memory never modeled.
## When to skip
Skipping is a first-class decision — even when the chart still looks persuasive:
- Checklist incomplete at 09:20 ET — observe or one pre-written A+ only.
- Live spread outside max for that symbol and session bucket.
- Index violently disagrees with a single-name thesis and no reduced-size RS plan is on the sheet.
- Platform, hotkeys, locate, or flatten path unverified after reconnect/update.
- Daily loss, PDT slot, or prop buffer tripwire already touched.
- News/FOMC/CPI window where the size-cut card says stand down.
## Closing
For **Level stacking: prior day H/L + VWAP + opening range**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.
- _posting_32_diagram.png (19.08 KiB) Viewed 52 times