Opening cross vs continuous-session fill budget
Posted: Fri Sep 11, 2026 9:49 am
Opening cross vs continuous-session fill budgets keep you from judging 09:30 fills with midday standards (and vice versa).
Execution quality is fill-to-plan adverse cents on your names at your TOD buckets — not a brand slogan. Size follows live spread width and session phase.
## Rails that stay on the sheet
- Cross continuous.
- Fill budgets by session phase.
- 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. Log adverse cents by TOD bucket (open vs midday) and by ETF vs single-name before changing venue folklore.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.
## Worked example — Opening cross budget ignored
Uses continuous-session fill assumptions on opening cross. Separate budgets: cross vs continuous slip; choose participation deliberately.
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 **Opening cross vs continuous-session fill budget** 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 **Opening cross vs continuous-session fill budget**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.
Execution quality is fill-to-plan adverse cents on your names at your TOD buckets — not a brand slogan. Size follows live spread width and session phase.
## Rails that stay on the sheet
- Cross continuous.
- Fill budgets by session phase.
- 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. Log adverse cents by TOD bucket (open vs midday) and by ETF vs single-name before changing venue folklore.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.
## Worked example — Opening cross budget ignored
Uses continuous-session fill assumptions on opening cross. Separate budgets: cross vs continuous slip; choose participation deliberately.
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 **Opening cross vs continuous-session fill budget** 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 **Opening cross vs continuous-session fill budget**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.