- never worked the runbook's 11x Dec-28 300/400 call tranche is not eleven spreads in the book, and the 90%-of-width trigger has never been measuring what it names.
Runbook Part 1 says 'BUY tranche 1 (~$100k): 11x Dec-28 300/400 combo and 10x Dec-28 350/500 combo'. The book holds 11x long GOOGL Dec-28 300C against exactly 1x short Dec-28 400C. The 350/500 tranche is intact, 10 long against 10 short. So ten of the eleven 400C short legs are not there. Part 2's row 'Any long call spread marks >= 90% of its width -> SELL that spread' has been reported every run as a single 300/400 percentage (42.3% today, 43.2% yesterday) computed off one short leg and applied to all eleven contracts. Those ten unpaired 300Cs are not naked - the 10x short 500C and 18x short 600C plus 1,543 GOOG shares more than cover them - but they are not the defined-width structure the runbook priced, and there is no width to be 90% of. rails.json does not cover the call side at all (its program is right:'P'), so nothing else catches this. This run does not edit rails.json or the runbook. Gabriel decides which one is wrong: the book, or the doc.
- never worked the SemiAnalysis composite has not been published since April, so the glut anchor is four months old.
Refetched gpu-index.semianalysis.com this run: its latest H100 composite is still Apr 2026 at $2.82, the same print the CSV captured on 08-18, with Mar $2.80, Feb $2.83, Jan $2.82 behind it. The monthly append is not being missed - the publisher has not printed May, June, July or August. That matters because runbook Part 5 arms the glut watch off 'SemiAnalysis composite; -20%+ in a quarter = tripwire, flat is pre-signal', and the CSV's own note on the Apr row reads 'PRE-SIGNAL tightening'. A composite that is flat because nobody published it is not the same fact as a composite that is flat because compute prices are flat, and the second reading is the one the doc invites. Every daily marketplace number this check prints is currently being anchored to a four-month-old benchmark.
- never worked rails.py tests every GOOGL price level against the GOOG quote.
Unchanged and still open, reported since 08-24. rails.json lists the campaign underlyings as ["GOOG", "GOOGL"] and rails.py loops them in order, taking the first with a quote and breaking. GOOG is first, so thesis_break, t2_weakness, t3_confirmation, washout_buy, no_chase, rule6_close_shorts and rule8_crash_powder are all measured against GOOG. Every one of those levels is written as a GOOGL level. Today GOOG is $341.05 and GOOGL $344.75, a 1.08% gap, so the script reads tranche 3 as 5.6% away while against GOOGL it is 4.4% away. No rail has flipped on this yet. This page shows the GOOGL number, matching the docs; the script's own output uses GOOG. This run does not edit rails.json.
- will happen again get_price_snapshot returned an empty prior_close on all thirteen tickers this run.
Worse than the recent pattern: ten of thirteen were empty yesterday midday, eleven of thirteen at yesterday's open, thirteen of thirteen today, so there was no populated field left to cross-check the workaround against. Prior close is derived as last minus the broker's own 'change' field on the same snapshot. Every derived value reconciles with the change_pct the broker returned beside it, so the day moves on this page are internally consistent, but today they are unverified against a second source.
- source broke Akash has printed identical rates for nine straight days.
The Akash weighted averages have been exactly $2.71 for H100, $4.45 for H200 and $1.71 for A100 on every day of the series since 08-18, to the cent, with a 0.0% day move again today. getdeploying moves a few cents day to day and SFCompute moves daily, so a genuinely pinned market across three accelerators for nine sessions is unlikely. Treat the Akash column as possibly cached rather than as nine flat observations. Not yet confirmed either way.