Briefing reference: /Users/dadbot/Desktop/ClaudeBod/projects/dadbrain/Analysis/briefings/2026-09-28-pm.md Scanner watchlist: intelligence/2026-09-28-watchlist.md (07:15 ET, firm-wide GO) PM: SLACK (sole member)
data-infra/regime/current.json (ASSAY, status: ok, as_of: 2026-09-22) — 4 sessions stale, read as reported: spy_day: flat · spy_open_to_close_pct: −0.08 · spy_vs_sma50: above 50d · spy_drawdown_bucket: <2% (spy_drawdown_pct −0.58) · vix_regime: LOW (<18) (vix 14.21).
Staleness named, not papered over: the file is now four sessions behind (09-23 → 09-28), and it is blind to this weekend — it was written before the Iran/Hormuz breakdown that produced this morning's gap-down bias. Its VIX (14.21) versus the briefing's live 16.40 (prior close 14.87) is the largest live-vs-file gap of the quarter, +2.19 points. Both still sit in the LOW (<18) bucket, so the regime label survives the lag — but the label is doing less work than usual today, and I will not let a 4-session-old file carry the read.
Charter consistency — consistent, with two indicators moving. Of the indicators named in my ratified ## Regime Charter (desk CLAUDE.md): spy_vs_sma50 = above 50d and spy_drawdown_bucket = <2% are the stale-but-as-reported state (the honest asymmetry stands — above-50d is the inferential bucket, N=42, and it is the one I sit in). vix_regime = LOW is the bucket in which my gate is silent by design; the charter says a step up the VIX ladder is what I want, not a threat. Two things are genuinely moving. (1) My own exceedance rate — re-measured this session on my own verified pipeline at the fixed 4.970946% threshold: dev (2020–2023) 15.01%, trailing-60 0/60 = 0.00% (0.00×), trailing-250 11/250 = 4.40% (0.29×) — fourth consecutive measurement short of the dev rate. (2) The shared VIX tag's direction — 16.40 is the closest this stack has been to the charter's own MID (≥18) shift condition in weeks, and per the charter a move into MID is one of my named shift triggers. It is not there; a 1.53-point single-day lift is a level change, not a regime change, and the charter's persistence rule (5 consecutive sessions in the new state) has not begun to run.
Today's plan — stand flat, change nothing — is consistent with the charter. On the exceedance reading the persistence rule is satisfied many times over, so it belongs in a proposal through the Desk Review shape (next monthly review), not in a unilateral move here. Watch and report only: I change no gate, no sizing, no posture, no script on a regime signal.
load_daily_through(), 2,195 daily rows through 09-25) rather than borrow or manufacture a print — and there is no IWM pre-market print available to me, so today's gap is inferred from the futures/QQQ bias, not observed. IWM 09-25 close 282.17 (open 282.34, high 283.52, low 280.455 — a +0.18% session); prior closes 281.67 (09-24), 282.03 (09-23), 287.21 (09-22), 285.62 (09-21), 284.18 (09-18), 285.33 (09-17), 283.88 (09-16), 285.25 (09-15). Trailing-20 closes 281.67–295.92, high 300.39, low 279.045; trailing-60 closes 281.67–305.01, high 305.18 → live structural refs ~$280 floor / ~$296–300 ceiling. Trailing-20 daily ATR 3.583 (1.27% of close). Reference legs: SPY 771.35 / QQQ 744.44 (09-25 closes, per the briefing). Flat book — state/position_ledger.json → {"open_position": null}.State-machine leg, stated plainly first because it is the leg the desk is built to report. agents/slack/state/position_ledger.json reads {"open_position": null}. Two of my three branches are dead on arrival: nothing is held, so no hold-silently marker today, and nothing to close, so no close-and-log due — no day-1..5 counter is running because no cycle was ever opened. Today is day 0 of a cycle that has not started: not an open day, not a hold day, not a close day — a no-signal day, and today's action is to stay flat and log no_trade:no_signal. The one branch that can log a real trade is an entry at today's open, which is gated by the run settling at the last completed close — the run ending 09-25's close, measured this session on my own pipeline at −0.7073% (282.17 / 284.18 − 1) against ±4.970946%. That is 4.26pp short on the down leg; the up leg is nowhere near either. Today's open is closed mechanically and my call is exact rather than probabilistic: p_trade 0.0, direction none, conviction high.
Scoreboarding my own last call, honestly. The 09-25 plan bound the roll and predicted −0.8832% for a flat close at 281.67, and called no flag at 09-25's close → no 09-28 entry. IWM printed 282.17, so the run settled −0.7073%: direction right, no-trade call right, roll bound 0.18pp off on a +0.18% session that ticked the base by a cent-and-a-half per share. That is the second consecutive time the bound-the-roll technique (committed 09-11, applied in-plan from 09-25) landed inside 0.2pp. I keep using it.
What would have to happen at today's close to matter at all. An entry at Tuesday 09-29's open (which would exit the close of 10-06) needs the run ending today's close to cross. The window's base rolls up from 284.18 (09-18) to 285.62 (09-21), so the dropped session pushes the reading ~0.33pp deeper before a tick of today's tape prints — a flat close at 282.17 already reads −1.2079%. Against the ±4.970946% flag: an up-flag needs a close ≥ 299.82 — a +6.25% session; a down-flag needs ≤ 271.42 — a −3.81% session. For scale: trailing-20 daily ATR is 3.583, about 1.27% of spot — so the up-flag asks for ~4.9σ and the down-flag ~3.0σ of a single session, on a name with no scheduled print of its own, in a news-driven two-sided tape. My call: no flag settles at today's close either. And I give the mechanic, not just the level, because that is the lesson: the reading moves on window composition — a large session rolling off the back has travelled it 2–3pp on a sub-1% tape, and today it rolls against me by a third of a point.
Setup present: no — mechanically excluded at today's open, and not plausibly reachable at today's close. Sizing vs. event risk: nothing to size today, and no override exists to apply. With p_trade 0.0 there is no notional, no entry window and no exit to adjust. The locked parameters stand unchanged: 15% of equity as fixed notional (≈$3,750 on the $25K account), single position at a time, no stop-loss, no profit target, no early exit. Today's HIGH event risk has no purchase on the size and no role in the exit (strategy_v2.md Rule 6) — but this is the day to state that precisely rather than lean on it, because the hold-spanning event question is live this week for the first time in a month, and I am answering it explicitly.
The 5-day hold spanning PCE (09-30) and NFP (10-02) — addressed head-on, because it is the real question. Any flag that settles this week produces a hold that carries both Tier-1 prints: a flag at today's close → entry 09-29's open → exit 10-06's close, so 2 of the 5 held sessions are Tier-1 print days; a flag at 09-30's close → entry into PCE day itself at 10-01's open → exit 10-07's close, spanning NFP and FOMC Minutes (10-07). That is the densest scheduled-event window of the quarter, and it is worth saying plainly what my mechanism does with it: nothing. There is no event-day override, no early exit, and no stop in the locked design, so a flag this week means the 15% notional is held through both prints by construction, not by choice. I will not invent a discretionary skip — that is a strategy change and it is TEMPER's, not mine. What I will do is pre-commit the language so it cannot be retconned later: the first live flag of Phase 3, if it lands this week, enters the largest hold-spanning event window this desk has ever run. The sizing is calibrated for exactly this class — the March 2020 COVID-week tail, −19.66% of notional on a long ≈ −3% of equity — and event risk is a carry cost here, not a gate input. The honest asymmetry: on a risk-off, higher-beta small-cap tape the down leg is the nearer route, which means the likeliest first flag is a contrarian LONG held across PCE and NFP — and my House Vesper obligation (the overnight-vs-intraday P&L decomposition by direction) is owed before any short flag settles, so the decomposable-before-entry leg is the up leg, not the one I actually expect. I am naming that gap rather than letting it pass silently.
Session-character fit: poor for intraday structure, irrelevant to me — and I say so instead of manufacturing a view. I have no intraday component: I check IWM once, at the open, and hold for five sessions. Two-tier rotation under a rising-rate ceiling, direction-unknown, no IWM pre-market print, and a headline clock that can flip the tech/growth polarity after the open are all precisely the conditions that do not manufacture a 5-day ±4.97% extent. This is now 60 consecutive logged no-signal sessions through 09-25 (07-02 → 09-25 unique; the duplicate 08-07 row stays flagged for cleanup and is not counted), and today would make it 61 once logged. The most recent settles are −0.77% (09-21) → +0.69% (09-22) → −0.65% (09-23) → −1.28% (09-24) → −0.71% (09-25) — a ±1.3% band, every reading 3.7–4.3pp short. The closest Phase 3 reading remains 09-16's −3.21% (1.76pp, a single isolated print that receded within two sessions); the deepest positive remains +3.92% on 08-06 (1.05pp). No cluster in either the −4.0%→−4.97% or the +4.0%→+4.97% band, in 60 logged sessions. SPRT at n=0, W0/L0, LLR +0.000, both boundaries (±2.944) untouched — and by construction it cannot flag at n=0, which is exactly why the exceedance test exists beside it. I want the flag; I do not expect it.
Key levels and invalidation. The binding level is the ±4.970946% 5-day run threshold, full stop; every other level is context. Measured structural refs: ~$280 floor (09-24 low 279.045; trailing-20/60 lowest close 281.67) / ~$296–300 ceiling (trailing-20 high 300.39, 60-day high 305.18). A decisive break of the floor is the realistic route to a down-flag (→ contrarian long), and this weekend's Hormuz breakdown is the most plausible source of the impulse that gets it there — but the gate needs a 5-session extension, not one gap-down day: even a −1.0% close today prints the run at only −2.20%, still 2.8pp short. Invalidation for today: none applies — flat, no entry reachable at either the open or a plausible close, no scheduled exit, nothing held into the Dallas Fed print, the bill auctions, or the Iran headline clock.
Rolling exceedance — fourth consecutive measurement, and the only live falsifier this stack has. Measured this session on my own verified pipeline with the threshold held at 4.970946%: dev-period (2020–2023) exceedance rate 15.01% (1,006 windows); trailing-60: 0 of 60 → 0.00% (0.00× the dev rate); trailing-250: 11 of 250 → 4.40% (0.29×). The caveat stays in front: overlapping 5-day windows are autocorrelated, so trailing-60 carries roughly 12 effective independent draws, not 60 — 0/60 is not the 1-in-17,000 event a naive binomial implies; even at ~12 effective draws the expected count is ~1.8 and I observed 0. Suggestive, not conclusive — and short of the dev rate for the fourth straight direct test. That is a finding, not a comfort, and I will not close this section with the line I retired on 09-23.
Proposed trigger — to TEMPER, not adopted unilaterally. Under my charter the persistence rule (5 consecutive sessions) is satisfied — the low-exceedance state has held the whole live run — so this belongs in a Desk Review shape, not a unilateral move. I propose: request a recalibration review when the trailing-250 exceedance rate is below one-third of the dev rate (< 5.00%) and the trailing-60 rate is ≤ 2.50%, sustained for 60 consecutive sessions. On today's measurement both conditions are met, so under the proposed rule the review would be requested. I am not filing it inside a daily plan — the next monthly Desk Review is the correct shape — and I am changing nothing: no gate, no sizing, no posture, no script. Stating the trigger so it is decidable is the entire point.
What I'm watching: (1) the run settling at today's close — the only number that matters, gating a possible 09-29 entry — bounded through the roll: base rises to 285.62, a flat close already reads −1.2079%, and a flag needs a +6.25% or −3.81% single-session close (~4.9σ / ~3.0σ of ATR); my call: no flag. (2) The ~$280 floor — a decisive break is the only realistic route to a down-flag, and this weekend's Hormuz rejection is the most plausible source; but the gate needs five sessions, not one gap-down day. (3) Whether VIX's +1.53 lift persists toward the charter's own MID (≥18) shift condition — five consecutive sessions would begin the persistence clock, and that is the state my mechanism actually wants. (4) My own exceedance rate — the fourth straight short reading; the trailing-250 refresh is the only thing in this stack's live history that can falsify a silent gate. (5) The event calendar, now genuinely live — any flag this week holds across PCE (09-30) and NFP (10-02), and I have named that exposure in advance rather than after the fact.
slack: p_trade 0.0, direction none, conviction high)no_trade:no_signal (blocked=run_magnitude; gating run −0.7073% vs ±4.970946% = 4.26pp short; flat book, no 5-day cycle in flight — not an open/hold/close day; next entry window = Tue 09-29's open only if today's close crosses ±4.97%, which would exit the close of 10-06 and hold across both PCE and NFP)## Regime Charter — no posture change. Exceedance proposal carried to TEMPER via the next monthly Desk Review; VIX's move toward the charter's MID condition named but not acted on (persistence clock not started). Nothing executed.No trades taken.