desk: reversal date: 2026-09-30 forecasts: "null": # quoted deliberately — a bare null key parses as None in YAML p_trade: 0.0 direction: none conviction: high meridian: p_trade: 0.0 direction: none conviction: high
Briefing reference: /Users/dadbot/Desktop/ClaudeBod/projects/dadbrain/Analysis/briefings/2026-09-30-pm.md PM: Wicker (persona; own stack retired 2026-07-14 — this plan covers active members Null + Meridian only)
Regime watch: data-infra/regime/current.json reads as_of 2026-09-22 — status ok: vix_regime LOW (<18, VIX 14.21), spy_drawdown_bucket <2% (−0.58%), spy_vs_sma50 above 50d, spy_day flat, spy_open_to_close_pct −0.08. The file is now SIX sessions stale — it contains none of 09-23/24/25/28/29/30 — so it is reported as read (not unavailable) and treated as directional only. A file six sessions behind cannot discharge the charter's 5-consecutive-session persistence check on its own; flagged for the operator.
Charter consistency (against the DRAFT direction — the charter in desks/reversal/CLAUDE.md is DRAFT — not ratified, and the 2026-09-25 peer review correctly caught an earlier plan calling it "ratified"): all three shared tags sit at the charter's baseline state (LOW / <2% / above 50d); the live print is the briefing's VIX 16.08, still LOW (<18), +0.04 on the day. No charter indicator is moving off baseline, no non-baseline state has held for the 5-session persistence rule, and no Desk Review proposal is triggered. One watch item, stated as a watch and not a finding: SPY now sits just below its 20-day SMA (764.38 vs 765.02, −0.08%) — a continued bleed is the direction that could eventually move the spy_vs_sma50 tag, but 20d ≠ 50d and I will not treat a 20-day cross as that tag moving. Today's plan is consistent with the drafted direction — intraday only, no overnight hold, no regime-keyed sit-out invented for either member (neither carries one), and no gate, size or parameter moved on a regime signal.
Clause-2 note: today is a deterministic Tier-1 skip, so the charter's clause-2 exposed case (Null repeatedly fading a persistent gap-down selloff into weakness) cannot fire — the event gate closes the session before any gap logic runs. Report only.
Setup present: NO TRADE — p_trade 0.00, direction none, conviction HIGH. PCE is a Tier-1 release and Null's live track runs is_event_day(trade_date, tier_filter=2); the event gate fires before gap measurement, so no qualifying gap is evaluated today. A deterministic Tier-1 skip is not a near-miss and must not be scored or narrated as one — it is the cleared filter working, and a 0.00 here is the honest, well-calibrated price (my own bucket table: 9 plan days priced 0.00, 0 fires).
Sizing vs event risk: standard, and moot today — 1 MNQ, 0.5% risk, one position at a time, 11:00 ET hard exit. The event gate returns before the fetch; no position can exist. No change to any cleared parameter.
Key levels (what the skip is standing down in front of): QQQ prior close 737.96 (fill target), prior high 740.37, prior low 735.39, SMA20 722.95 (the filter that decides eligibility — price +2.08% above, so a gap-down long would have been the aligned side and a tiny gap-up the exception), ATR(14) 9.87. Live zones if the gate had not fired: [737.96, 740.92] (tiny gap-up SHORT) ∪ [731.05, 736.97] (gap-down LONG).
Invalidation / stand-down: the whole session — the Tier-1 PCE gate closes it. No gap, band, drive or retrace is evaluated. The 11:00 ET hard exit is unchanged.
The specific structural question I am watching post-release (not filler): today is a live test of whether the Tier-1 skip costs edge or protects it. The 2026-06-18 observation on this exact stack was that the PCE/FOMC skip prevented a losing fade — a small overnight gap that passed the size and vol filters was overrun, not filled, on a Tier-1 day. So I am watching, after 8:30 ET: (a) the sign and size of the cash-open gap — does it land in a qualifying band at all ([737.96, 740.92] or [731.05, 736.97]), i.e. would the skip have suppressed a real setup?; and (b) whether the reaction tape was one-way or two-sided — a one-way PCE reaction gives no open drive and no ≥50% single-candle retrace (the 09-24 max_retrace_ratio=0.00 pattern), in which case the pattern gate would have blocked the fade anyway and the skip cost nothing. Recording the answer as a data point on the skip's protective value — an observation, no gate touched.
Mechanism health (read-only): SPRT CONTINUE — n=17 W15/L2, LLR +2.168, cumulative +$1,898.25 net / +$1,906.75 gross, WR 88.2%, 0.777 from the CONSISTENT-WITH-BACKTEST boundary. First-loss watch N=2 — 09-03 and 09-28 are the same mechanism-level shape (a counter-trend fade against a one-way session drive, stopped inside 15 minutes, both LOW-VIX). Desk tripwire is N ≥ 3 → a filter/stop question to TEMPER, as a question. Armed, not triggered; no gate or parameter touched. A skip day cannot advance it.
Null — p_trade-bucket calibration table (DELTA's ask; 52 scored plan days through 09-29, 15 fires, realised 0.288):
| p_trade bucket | N plan days | fires | realised freq |
|---|---|---|---|
| 0.00 | 9 | 0 | 0.000 |
| 0.01–0.09 | 1 | 0 | 0.000 |
| 0.10–0.14 | 2 | 0 | 0.000 |
| 0.15–0.19 | 6 | 3 | 0.500 |
| 0.20–0.24 | 6 | 1 | 0.167 |
| 0.25–0.29 | 7 | 1 | 0.143 |
| 0.30–0.39 | 6 | 2 | 0.333 |
| 0.40–0.49 | 10 | 6 | 0.600 |
| 0.50+ | 5 | 2 | 0.400 |
Read: broadly calibrated in aggregate. 0.20–0.29 remains the over-priced zone (realised 0.143–0.167 over 13 days) while 0.40–0.49 is the best-realised bucket (0.600 at N=10). Yesterday's 0.42 was a miss on a hard trend-filter block (09-29: blocked=trend_alignment gap_up=True above_sma20=True gap_ratio=0.401), scored Brier 0.1764 = (1 − 0.42)². That is the second consecutive over-price of a small-gap-up path that the trend filter refused — carried as a calibration observation, no gate change. Today's 0.00 sits where a deterministic gate puts it.
Setup present: NO TRADE — p_trade 0.00, direction none, conviction HIGH. PCE is a Tier-1 release; paper_trade.py calls is_event_day() and returns before the per-symbol data fetch (the gate that was log-only and fixed 2026-07-14). So no leg is evaluated today. Direction is none rather than the mechanical short because no trade can fire — a lean that cannot be acted on is not a forecast.
Sizing vs event risk: standard, and moot today — $250/leg, caps 10 MNQ / 5 MES / 5 M2K, 2-loss daily cap, hard close 11:30 ET. The same-sign stop guard voids any malformed stop (live since 2026-08-20). No change to any cleared parameter.
Key levels (what the skip is standing down in front of): QQQ prior high 740.37 (sweep level, +0.33% above prior close 737.96); SPY prior high 766.85 (+0.32% above 764.38); IWM unavailable. ADX band 18–32. Volatility precheck (reads yesterday's range): QQQ prior range 4.98 vs ceiling ≈ 9.33 (1.25 × ~7.46 avg, cache basis) → passes at ~0.53×; SPY prior range 4.50 vs ceiling ≈ 6.24–6.32 → passes at ~0.72× — so, unlike 09-29 (QQQ blocked), both priced legs would clear Step 1 today, and on a live day the binding gates would be ADX and sweep/exhaustion, not volatility.
Invalidation / stand-down: the whole session — the Tier-1 PCE gate closes it. No volatility, ADX, sweep or exhaustion step is evaluated. The 11:30 ET hard close and the 2-loss daily cap are unchanged. I do not touch the RSI(2) ≥ 88 line: cleared-parameter territory, only TEMPER can move it.
The specific structural question I am watching post-release (not filler): with both priced legs passing the volatility gate, the volatility block that bound yesterday is gone — so the live question is whether a PCE reaction session produces the shape this mechanism needs. The briefing's own read is the discriminator: a fade is credible only after an opening extension stalls and the release reaction fails to broaden. That is exactly Meridian's setup — an upside extension into QQQ 740.37 / SPY 766.85 that stalls and fails to broaden is a sweep candidate; a one-way gap reaction that never tags the level is no_sweep (the 09-28 shape, on all three legs). So I am watching, post-8:30: (a) does price rally into a prior high at all, or gap away from it; (b) if it tags, does the RSI(2) read finally print ≥ 88 — the last filter is 0-for-12 live, closest IWM 84.2 (09-21); and (c) does the release reaction broaden (which would make any up-move a trend leg, not an exhausted push). Recording the answer as a data point on the sweep-tag / exhaustion-filter question — an observation, no gate touched.
Mechanism health (read-only): SPRT CONTINUE — n=3 W2/L1, LLR +0.222, cumulative +$385.22, WR 66.7%; spy_leg n=1 WR 100%; iwm_leg n=0 (honest live anchor ~56%, not the 73.3% headline). No tweak proposed.
Meridian — p_trade-bucket calibration table (DELTA's ask; 52 scored plan days through 09-29, 2 fires, realised 0.038):
| p_trade bucket | N plan days | fires | realised freq |
|---|---|---|---|
| 0.00 | 7 | 0 | 0.000 |
| 0.01–0.09 | 6 | 0 | 0.000 |
| 0.10–0.14 | 10 | 1 | 0.100 |
| 0.15–0.19 | 6 | 1 | 0.167 |
| 0.20–0.24 | 11 | 0 | 0.000 |
| 0.25–0.29 | 6 | 0 | 0.000 |
| 0.30–0.39 | 6 | 0 | 0.000 |
Read: 23 plan days priced ≥0.20 have produced zero fires; both scored fires landed at 0.10–0.19. The desk's historical mean p of ~0.15 against a realised 0.038 is the honest diagnosis of the over-pricing habit; today's 0.00 is set by a deterministic gate, not by that habit.
Standing tolerance (DELTA's ask, enforced): if Meridian produces two consecutive non-fires while this desk calls the setup "one gate away", the label reverts from regime to calibration and the price drops to the realised bucket frequency. Today the desk does not make that claim — a Tier-1 skip is not "one gate away," it is a closed session. Tolerance armed, not triggered.
is_event_day(trade_date, tier_filter=2), Meridian is_event_day() (returns before the per-symbol fetch). Null p_trade 0.00 / direction none / conviction high; Meridian p_trade 0.00 / direction none / conviction high.no_sweep), and whether a tag would finally print RSI(2) ≥ 88 (0-for-12 live).DRAFT — not ratified status; (b) the "mutual exclusion" structural law stays retired and the sweep count stays 0-for-12; (c) the ADX-floor TEMPER question stays filed as a question with the in-band-but-no_sweep counter-evidence attached — and I mint no new structural law today; (d) DELTA's p_trade-bucket tables are maintained and advanced through 09-29; (e) no miss is filed as "REGIME" — today's 0.00 is a deterministic gate, stated as such.strategy_v7.md); standing ~6-month decay re-backtest next due ~2027-02-20. Wicker's feed/session re-run remains the desk's highest-priority open reconfirmation (own stack retired, not a today blocker).data-infra/regime/current.json — as_of 2026-09-22 (SIX sessions stale; directional only) — vix_regime LOW (<18), spy_drawdown_bucket <2%, spy_vs_sma50 above 50d; no charter indicator off baseline, none moving for the 5-session persistence window; consistent with the DRAFT Regime Charter; no Desk Review proposal.No trades taken.