desk: house-delta date: 2026-09-30 forecasts: delta: p_trade: 0.0 direction: none conviction: high
Briefing reference: /Users/dadbot/Desktop/ClaudeBod/projects/dadbrain/Analysis/briefings/2026-09-30-pm.md PM: DELTA (independent read of my own desk — D3 superseded 2026-09-23; this is House Delta's own opinion, not a blend)
data-infra/regime/current.json (read 2026-09-30, status: ok): as_of 2026-09-22 — SPY day flat (open-to-close −0.08%), above 50d, drawdown bucket <2% (−0.58%), VIX 14.21 LOW (<18). The file now lags the live tape by six sessions (09-23, 09-24, 09-25, 09-28, 09-29 and today are not reflected). It is a dated read, not a stale-missing one — I name it as behind the tape rather than writing unavailable, the convention my last five plans used.
Consistency with House Delta's ## Regime Charter (desks/house-delta/CLAUDE.md, header still DRAFT — not ratified): consistent; no non-baseline tag is active. Walking the charter's own indicator list (item 5) against the file and today's live tape: spy_drawdown ≥ 5% — no (<2% at the file's read; Tuesday's mild tape does not approach it); vix_regime MID or HIGH — no (file 14.21 and today's live 16.08 both sit inside LOW (<18)); spy_vs_sma50 below 50d — not measured: the file's dated tag says above 50d (as of 09-22), and today's briefing carries SPY barely below its SMA20 (764.38 vs 765.02) but no current SMA50 level, so proximity to that tag is unmeasured, not "close". Nothing in today's plan changes posture: long-only, intraday, flat by 15:30, one position — and today no posture is expressed at all, because the session is a hard skip.
One reading worth naming precisely, not a shift: VIX held at 16.08 (+0.04 vs prior close 16.04) and remains deep in the favorable bucket — 13.92 points below my 30 hard skip and inside LOW (<18), my best-backtested LONG bucket (own tabulation: VIX < 18 PF 2.22, n=62; 18–28 PF 1.62). A tag change needs the same non-baseline tag for 5 consecutive sessions; the tag is still baseline.
Own-desk charter watches: rolling 6-month PF reads 1.648, alert OFF — carried as the demonstrated instrument finding (a fixed trailing-180d window holding the whole book is cumulative PF under another name; the on/off state is one trade's gross P&L against a fixed loss base); no escalation filed on the OFF print. Per-pair PF: AMD→TSM n=11, WR 45.5%, PF 1.346 (above 1.0 for the first time, no recovery declared), NVDA→ASML 2W/0L, +$264.42. Watch and report only — a persistent shift becomes a Desk Review proposal (recalibration / sit-out / new-mechanism), never an automatic change, and I touch no gate.
Call: p_trade 0.00, direction none, conviction high. Setup present no — the session is a hard skip, and this is a rule, not a forecast.
My signal is a leader's first-hour return off the 09:30 cash open, read at 09:55, versus ±1.5%: NVDA ≥ +1.5% → buy ASML at the 10:00 bar (primary, edge-carrying cell), AMD ≥ +1.5% → buy TSM (secondary). A leader ≤ −1.5% is my disabled-SHORT branch (ENABLE_SHORT = False) — no trade by rule. Today none of that runs: August PCE / Core PCE at 8:30 AM ET is one of my four hard skips, so paper_trade.py will log no_trade:hard_event:PCE and no signal is evaluated. p_trade 0.00 is a structural certainty, not a market read, and it is the one honest number for a day the rule closes. direction: none because there is no first trade to lean; conviction: high because the rule is deterministic — a hard skip is the highest-confidence no-trade state the stack has, and pricing anything above 0.00 here would be a forecast against my own gate.
Why 0.00, stated against my own bucket arithmetic. intelligence/plan-calibration.csv, my rows, as of today (51 scored days, 9 fires, unconditional realized fire rate 0.176, mean forecast 0.178):
| p_trade bucket | scored plan days | fires | realized fire rate |
|---|---|---|---|
| 0.00–0.10 | 13 | 0 | 0.000 |
| 0.12–0.15 | 15 | 4 | 0.267 |
| 0.18–0.25 | 13 | 2 | 0.154 |
| 0.30+ | 10 | 3 | 0.300 |
| all | 51 | 9 | 0.176 |
The 0.00–0.10 bucket is 13 days, 0 fires, realized 0.000 — and the four sessions that sit in it as hard skips (07-14 CPI, 08-12 CPI, 08-26 PCE, 09-04 NFP) never fired, exactly as the rule guarantees. 0.00 is the only number consistent with that record. I am not pricing a hard skip at 0.02 or 0.05 to "leave room": there is no tape state, no pre-open signal, and no leader impulse that can produce a trade today, because the gate fires before the signal is read.
Sizing vs. event risk: not applicable — no trade, no sizing. The standard is 0.75% single-position risk, one position at a time, and nothing is adjusted because nothing is taken. There is no thin-tape size-down to invent and no headline buffer to add: on a PCE day my exposure is structurally zero, which is precisely the protection the hard skip exists to provide — the 8:30 print and its rates/quarter-end aftershock land entirely outside any position of mine.
Session-character fit: incompatible by rule. My mechanism needs a large idiosyncratic first-hour leader impulse that the laggard has not yet followed. A PCE morning is exactly the tape where a semiconductor "impulse" is most likely to be macro beta — a whole-complex repricing on the rates/inflation surprise rather than a design→manufacturer cascade — which is the structural reason the skip exists (macro events can break the lead-lag transmission, TEMPER's 2026-06-24 clearance language). Even if a leader clears ±1.5% today, the clear would be suspect: the leader-vs-basket residual is the discriminator that decides whether a clear is idiosyncratic, and a one-factor macro repricing is the stand-down shape by construction. The skip sidesteps that question entirely.
Key levels (mine only): the only load-bearing numbers are each leader's first-hour return off the 09:30 cash open, read at 09:55, versus ±1.5% — NVDA ≥ +1.5% → buy ASML (primary, edge-carrying, live 2W/0L +$264.42 — unseen since 2026-08-03, ~8 weeks); AMD ≥ +1.5% → buy TSM (secondary, n=11, WR 45.5%, PF 1.346). None of them is a trade input today. Index gap-framing only: SPY 762.35 / 766.85 (range), SMA20 765.02, ATR 6.97; QQQ 735.39 / 740.37 (range), SMA20 722.95, ATR 9.87. Carried data gap: the non-firing pair's first-hour value is still unrecorded on traded days, and on hard-skip days no leader value is recorded at all (the hard_event rows carry empty leader_return_pct) — which is the exact measurement today's structural question needs, and I cannot obtain it from the pipeline.
Invalidation / no-trade reasons (all binding today):
no_trade:hard_event:PCE by rule; the session is closed to me before any signal logic. No size, no buffer, no exception.Today is not filler: it is a free, live observation of the open item TEMPER flagged at my 2026-06-24 clearance and that I have never run — the event-day diagnostic (re-run with FOMC/CPI/NFP/PCE skips disabled) to confirm the skip is a defensible protection rather than a missed-opportunity filter. Every hard-skip session is a natural experiment I currently throw away: the rule closes the session, and the pipeline records no leader value, so I never learn whether a PCE-day cascade was there to be traded.
The specific question: does today's post-PCE first hour produce a ≥1.5% idiosyncratic semiconductor leader impulse — a cascade my mechanism would have taken — or is the post-release tape a one-factor macro move with no leader-specific content? I will read and record NVDA's and AMD's first-hour returns off the 09:30 print at 09:55 (by hand — the pipeline will not, on a skip day), and note whether any clear is leader-specific or basket-wide. One observation is not evidence to change the skip (my own N≥3 discipline, and the peer-review pattern the firm is watching on this desk is a two-observation update — I will not repeat it); it is the first row of the event-day diagnostic's data, to be accumulated across PCE/CPI/NFP/FOMC days until the question is decidable. No gate is touched, and no proposal is filed off today. If a cascade appears repeatedly across many skip days with genuine idiosyncratic content, that is a Bench / Desk Review question about the skip's scope — never a unilateral change.
Desk book state (carries forward, unchanged by today's plan). Cumulative +$566.45 across 13 LONG trades, 7W/6L, WR 53.8%, gross PF 1.648; SPRT n=13, LLR +0.976, CONTINUE (+1.969 to CONSISTENT-WITH-BACKTEST, −3.920 to DEGRADED). NVDA→ASML 2W/0L, +$264.42 — the edge-carrying cell, starved ~8 weeks (unseen since 08-03), regime-shaped, not a gate problem (VIX < 18 is my best bucket and inside it the tape is quiet). AMD→TSM n=11, WR 45.5%, PF 1.346 — above 1.0 for the first time on three consecutive wins, no recovery declared (one of the three, 09-22, is measured sector beta); the 09-05 stop-calibration diagnostic read NO and remains pending TEMPER cadence-ratification via the 2026-09 Desk Review. Rolling 6-month PF 1.648, alert OFF (instrument artifact, above). SHORT re-enablement rejected 2026-07-15 — live gate stands; the governing path (30 LONG trades at PF ≥ 1.5) is at n=13, 17 trades from even being decidable. Stand-down argument live and provisional; withdrawal needs AMD→TSM PF > 1.0 at n ≈ 15+ (now n=11). Most recent live session: 09-29 no_signal (AMD first-hour +0.97%, 0.53pp short; NVDA −0.45%) — a quiet tape, no leader impulse.
Operational item (desk-top, carried): runner-health-2026-09-25 recorded delta: completed, daily artifact present, state ok — clean sessions after six September watchdog flags; 09-28 and 09-29 both produced normal rows. But the ledger-freshness post-run check is still unwired, so a clean run is being observed by me, not verified by the pipeline. Today the forecast is 0.00, so the scoring exposure is minimal: even if the watchdog trips, the EOD score for a hard skip is a mechanical no-trade and cannot be corrupted by a missing row — but I note the check remains unwired.
p_trade 0.00, direction none, conviction high. August PCE is one of my four deterministic calendar skips (FOMC/CPI/NFP/PCE), so the session is closed before signal logic; no_trade:hard_event:PCE is the expected row. No sizing, no parameter adjustment, no exposure — the skip puts the 8:30 print and its rates/quarter-end aftershock entirely outside any position of mine. Structural question watched post-release (the open event-day diagnostic): does the post-PCE first hour produce a ≥1.5% idiosyncratic semiconductor leader impulse — a cascade my mechanism would have taken — or a one-factor macro move with no leader-specific content? I will read and record NVDA/AMD first-hour returns by hand (the pipeline does not, on a skip day); one observation is not evidence, no gate touched, no proposal filed — it is the first row of the diagnostic TEMPER recommended, not a two-observation update. Next possible live session: Thursday Oct 1.No trades taken.