Unleveraged Hybrid Core Doctrine

[NYC88]

Hybrid here means: mechanical filters + discretionary trigger. Unleveraged core means: the account that pays rent is not running on max margin cosplay.

I run tools that make rules faster. I do not let tools invent rules mid-trade. That distinction is the whole doctrine.

Doctrine

1. Core book trades cash-like risk: size from daily DD and per-trade R, not from "buying power porn."
2. Filters are mandatory (session window, spread gate, event gate, VWAP/OR context per playbook).
3. Triggers are discretionary but must be named (`OR_HOLD`, `VWAP_CONT`, etc.).
4. Leverage / prop / options overlays are separate books with separate breakers — never silently merged.
5. Survival > optimization — a flat week obeying doctrine beats a clever week that voids the breaker.
6. Tools serve doctrine — Pine HUD, hotkeys, VPS exist to execute rules faster, not to invent new ones mid-trade.

Daily tick (mechanical, not woo)

Code: Select all

[ ] Core size capped
[ ] Breaker set
[ ] Filters on
[ ] Named setups only
[ ] No revenge add-ons
[ ] Separate books not merged

What "unleveraged" means in practice

Not "never use margin." It means your default size assumes you can eat a full daily breaker without account death or forced liquidation drama. If a normal loser sequence requires prayer, your core is leveraged in spirit.

Scalping culture drifts toward speed and size. Doctrine drifts it back toward repeatable process. Disagree? Bring journal stats — not adrenaline.

Do you keep prop/options overlays as separate books with separate breakers?
Named setups only — what's on your allowed list this month?
Can your core eat a full daily breaker without drama — honestly?
What tool most often tempts you to invent a rule mid-trade?

[Fairman]

Unleveraged hybrid core is a useful doctrine when "hybrid" means clear buckets — not a vague mix of styles that excuses every impulse. For stock scalping I keep a core that does not need leverage to pay the rent, then a small satellite for discretionary tape work.

Replying in-thread with operable constraints — not forum combat. If these rails disagree with your framing, treat it as a checklist offer.

Risk rails are mechanical: daily R, PDT slots, post-loss pauses, news size-cuts. Flat is a position. Skipping is a first-class journal row.

## Rails that stay on the sheet
- Hybrid means clear buckets.
- Vague mix excuses chaos.
- 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. Daily breaker and emotional no-new-size states are hard stops on behavior — not suggestions.
5. Tag the trade or the skip the same day — Sunday-you cannot fix what Monday-you did not name.

## Worked example — Vague hybrid mix
Hybrid used to excuse random style switching. Doctrine: clear buckets — scalp sleeve vs swing core — separate risk, journals, times.

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 **Unleveraged Hybrid Core Doctrine** 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 **Unleveraged Hybrid Core Doctrine**, keep operable boredom: written rails, measured cents, index context when relevant, and a skip that needs no apology. Process quality beats ticket volume.