2026-09-05 · midday

Markets are shut - it is Saturday, so this slot re-read the same finished Friday session the 06:35 run read. The book came back field-for-field identical: the same 32 legs, the same 32 marks, net liquidation the same to the cent at $1,428,489.17, and all thirteen quotes carrying the same last-trade timestamps. The same three structural rails are open, every runbook trigger is clear, and the standing long-leg repair reprices to the same $18,770. The only genuinely new thing this run found is in the check itself: this morning's report left out the delta block rails.py produced, so the page shows no delta ratios and still lists the top-2 delta rail as never measured, when the same run measured it at 0.67 and clear.

What to do

280P x5 and 300P x8 sit above the $260 long-leg ceiling.
BUY TO CLOSE 5 GOOGL Dec15'28 360 PUT / SELL TO CLOSE 5 GOOGL Dec15'28 280 PUT
one spread, limit, day · ~$18,770 debit ($37.5392 net per spread on this run's marks)
Your playbook: “long leg never above $260 (must sit at or above the $230-250 floor zone, never below $230)”
The same standing order, repriced from the book's own marks and landing on exactly the same $37.5392 as the 06:35 run - both legs are the same closing marks on a shut book, so an identical price is what a correct reprice looks like here, not a coincidence. Only the 5x 280P leg is reachable by this order; the 8x 300P leg has no written repair. This is a Monday order.

Still over, unchanged

These fire every run until you act on them. No order attached.

rail	now	limit
long_leg_band	280P x5, 300P x8	$230-$260 band	13 contracts outside
net_cash_ratio	-0.065	amber -0.05, red -0.10	amber
gross_leverage	1.741x	amber 1.30x, red 1.50x	red
top2_name_delta_ratio	0.67x	amber 0.70x, red 0.85x	clear
total_delta_ratio	0.94x	amber 1.30x, red 1.50x	clear

Why each one reads the way it does

long_leg_band
The rail the action item above addresses. Unchanged from the open run - no leg was traded and no mark moved.
net_cash_ratio
Cash -$93,230.12 against NLV $1,428,489.17, both identical to the open run, so the ratio is identical too.
gross_leverage
Gross $2,487,660.42 over NLV $1,428,489.17, unchanged. Carried caveat: this divides GROSS position value by NLV against thresholds the IPS wrote for delta notional, and the delta rows in this same table read 0.67x and 0.94x, so the red reading overstates true leverage.

delta by name

Delta notional per name as of 2026-09-05: stock at delta one, each option leg at the Black-Scholes delta implied by its own mark. Top two: GOOG, MU.

name	delta notional	of NLV
GOOG	$808,614	56.6%	1543 sh, 16 legs
MU	$142,658	10.0%	525 sh, 2 legs
META	$88,589	6.2%	144 sh, 0 legs
VOO	$87,042	6.1%	123 sh, 0 legs
RDDT	$79,258	5.5%	513 sh, 0 legs
NVDA	$50,998	3.6%	285 sh, 2 legs
INTC	$28,767	2.0%	300 sh, 0 legs
AMZN	$25,830	1.8%	100 sh, 0 legs
BRK B	$20,220	1.4%	40 sh, 0 legs
EQT	$11,034	0.8%	200 sh, 0 legs
TSLA	$353	0.0%	1 sh, 0 legs
DIS	$105	0.0%	1 sh, 0 legs

Everything else clear

Nearest trigger is GOOG - tranche 2 weakness (nearest written level, and what rails.py reads) at $317, 6% away.
TSLA -6.2%, now $352.89. No written rule for it.
Friday's move, re-read unchanged. The position is one share, about $24. No written rule, so nothing is proposed.
MU +5.9%, now $1,014.91. No written rule for it.
Friday's move, re-read unchanged. Micron is not a program in rails.json, so nothing is proposed off the move itself. The runbook's own MU row was swept again this run and is clear: the $1,250 collar-roll level is 23.16% away.

All 24 triggers swept, with today's number

price trigger	now	fires at	distance
GOOG - tranche 2 weakness (nearest written level, and what rails.py reads)	$335.72	≤ $317	5.6% down
GOOGL - tranche 3 confirmation	$338.72	≥ $360	6.3% up
GOOGL - tranche 2 weakness	$338.72	≤ $317	6.4% down
GOOG - tranche 3 confirmation	$335.72	≥ $360	7.2% up
GOOGL - thesis break, close regardless of price	$338.72	≤ $280	17.3% down
MU - roll the collar	$1,014.91	≥ $1,250	23.2% up
GOOGL - Rule 8 crash powder / washout buy	$338.72	≤ $260	23.2% down
GOOGL - do not chase strikes past here	$338.72	≥ $430	26.9% up
GOOGL - Rule 6, close every short put	$338.72	≥ $434	28.1% up
GOOGL - long spreads near max	$338.72	≥ $500	47.6% up
GOOGL - shares capped by the 600Cs	$338.72	≥ $600	77.1% up

level trigger	now	fires at	distance
Dec-28 30-delta put IV	35.7%	> 43%	+7.3 pt
GOOGL IV, crash trigger	35.7%	> 50%	+14.3 pt
11x Dec-28 300/400 call spread, mark vs width	42.05%	>= 90%	+47.9 pt
8x Sep-27 300/440 call spread, mark vs width	38.51%	>= 90%	+51.5 pt
10x Dec-28 350/500 call spread, mark vs width	29.29%	>= 90%	+60.7 pt
GOOGL Dec-28 340P extrinsic	$56.49	< $5	$51.49
Excess liquidity / NLV	74.41%	< 40%	+34.4 pt
NLV change on the week	+0.70%	-8% in one week	+8.7 pt
Defined max loss vs program cap	$175,059	$200,000	$24,941 headroom

calendar	date	away
Wash-sale window opens for the 6/05 GOOG loss lots	2026-09-17	12d
Micron fiscal Q4 print (not a runbook trigger row)	2026-09-30	25d
Alphabet Q3 print - scheduled thesis adjudicator	2026-10-28	53d
Reserve deploys at market if no crash by this date	2026-10-29	54d

Spot prices

	last	day
GOOG	$335.72	-0.9%
GOOGL	$338.72	-1.0%
MU	$1,014.91	+5.9%
AMZN	$258.30	-0.2%
BRK B	$505.50	-0.5%
DIS	$105.18	-1.8%
EQT	$55.17	-0.8%
INTC	$95.89	+4.6%
META	$615.20	+0.7%
NVDA	$229.49	+0.5%
RDDT	$154.50	-1.0%
TSLA	$352.89	-6.2%
VOO	$707.66	-0.4%

The check itself

found this run this morning's report dropped the delta block, so the page shows no delta ratios and contradicts its own run.
rails.py measured both Rule 1 delta rails at the 06:35 run - top-2 name delta 0.666x against a 0.70x amber, total delta notional 0.940x against 1.30x, both clear. The report written from that run has no `delta` key at all. The generator reads `delta` to render those two rows and the per-name delta table, so today's page shows neither, while the same page's gaps list still says top-2 delta 'needs per-leg option deltas, which summary.json does not carry' and is 'unmeasured'. That sentence was true before rails.py started computing deltas and is now false. Two consequences: the page understates what is measured, and the net-cash amber's no-new-delta clause is described as having no verdict when it does. This run carries the delta block verbatim and drops the stale gap line.
found this run on a weekend the midday slot can only re-read what the open slot already read.
This run's pull is field-for-field identical to the 06:35 run: same 32 contract_ids, same 32 marks, NLV, cash and gross position value equal to the cent, all 13 quotes equal including their last-trade timestamps (1788565824-1788566398, 19:50:24-19:59:58 ET Friday), and the same FROZEN top_status on every one. Nothing in a rail's inputs can change between two runs on a shut market, so the second run's verdicts are determined before it starts. This is the visible cost of the cron having no trading-day guard, already recorded as a gap - it is not just that the check runs on a closed market, it is that it runs twice.
will happen again the shut-book IV artifact reappeared, as expected.
The GOOGL Dec-28 340P returned option-midpoint-iv annualIv -15.874 with isValid false again - the known closed-book defect, previously seen on 08-23, 08-29, 08-30, 09-03 and this morning. implied_vol's valid 0.35677 was used, as on every prior occurrence. Recorded as confirmation, not as a new fault.

Rails that could not be evaluated

stressed_excess_liquidity - needs IBKR Risk Navigator (-30% price, +50% IV) with the TWS gateway up. Never yet measured, and the IPS amber's 7-day stress re-run has never run.
short_dec28_340p_extrinsic is still listed unmeasured in rails.json because it needs a live Dec-2028 chain pull, though the runbook's own version of the row was swept by hand this run and is clear at $56.49 against the $5 trigger.
gross_leverage divides GROSS position value by NLV against thresholds the IPS wrote for delta notional, so the red reading overstates true leverage. Unchanged and unresolved.
rails.py reads GOOGL levels off the GOOG quote, which is why the tranche-2 and tranche-3 distances differ between the two tickers in this report.
rails.py keys option-leg matching on contract_description with no contract_id fallback.
The 11x Dec-28 300/400 line is 11 long 300C against 1 short 400C, not eleven matched spreads.
The MU collar roll cannot be executed as the runbook writes it: Part 2 says 'BUY back 1400C' but there is no 1400C - the collar is 5x Dec-28 1740C short against 5x 900P long. Only the trigger row and IPS Rule 7 line 242 are stale; the book-summary line and the tax documents are already correct. First reported 08-18, and now 23% from firing.
The book's marks are extended-hours prints, not the official regular-hours closes the written rails say they read. Found and detailed at the 06:35 run; unchanged and unresolved.
The SemiAnalysis composite is five months stale at 2026-04 $2.82 and the written GPU tripwire is defined on it.
gpu-spot-daily.csv still has no 2026-08-29 row.
The GPU intraday health check still cannot see a capture that ran and collected nothing - a row that exists but is empty raises no warning.
Seeking Alpha still 403s every headless route, so it is readable only through your Chrome and only as free-tier previews.
finviz ratings tables remain unusable for recency on both names.
The cron '35 6,12' still has no timezone anchor and no trading-day guard, so it ran twice today against a closed market.

Where the numbers came from

Market CLOSED - Saturday. All 13 equity quotes came back top_status FROZEN, carrying Friday 2026-09-04's finished session, the same session the 06:35 run read.
get_account_positions, get_account_summary and get_price_snapshot all succeeded on the first call. The run fired 11:39 CDT / 09:39 PT.
Run label decided from the rails log rather than the clock, per the rule written into the bootstrap on 09-03: an entry for today already said markets-open, so this is the midday run. The machine clock reads CDT and the slot is defined in Pacific, which is exactly the case the log rule exists for.
Book identical to the 06:35 run: 32 rows, the same 32 contract_ids, zero quantity differences, and 0 of 32 marks different. On a live session an all-identical mark set would mean a stuck feed; on a shut market it is the correct reading.
Account summary identical to the cent on all four rail inputs: NLV 1,428,489.17, cash -93,230.12, gross 2,487,660.42, excess liquidity 1,062,952.61.
prior_close SERVED on 13 of 13 for a second consecutive run. Every one matches its own last-minus-change derivation.
contract_description present on all 32 rows, so defined max loss prints the complete $175,059 and uncapped_shorts was measured rather than skipped: 10 GOOG short against 10 long, 30 GOOGL short against 38 long, zero uncapped.
IV: the shut-book artifact again on the GOOGL Dec-28 340P; implied_vol's valid 0.35677 was used. Two-sided bid-ask 56.65/58.05 on the frozen book.
Every Part 2, 3 and 4 runbook trigger row was walked by hand against this run's numbers. All clear.
The delta block is rails.py's output copied verbatim, as the prompt requires - the first report in the series to carry it.
Weekly NLV comparison is against 08-29 midday, the previous Saturday run - also a frozen book carrying the prior Friday's close, so the two are directly comparable.