- 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 PUTone spread, limit, day · ~$19,448.05 debit ($38.8961 net per spread on this run's live marks)
Your playbook: “long leg never above $260 (must sit at or above the $230-250 floor zone, never below $230)”
Eleventh read of the same standing order, and the cheapest since Tuesday. The series: $18,769.60 on six frozen-market runs, $18,793.92 on Tuesday's live chain, $19,885.61 Wednesday morning, $19,570.59 Wednesday midday, $19,996.15 this morning, $19,448.05 now. This morning's page declared the $139-per-dollar-of-GOOGL sensitivity broken, on the grounds that GOOGL was 52 cents higher than the day before while the debit was $110.54 higher. Today's larger move argues the other way: GOOGL is $3.87 higher than at the open run and the debit is $548.10 lower, which is $141.60 per dollar, within two percent of the rejected figure. A 52-cent sample cannot test a rule of this size - a quarter of a vol point of skew moves the debit more than 52 cents of spot does. Skew did also help here: solving each leg off its own mark puts the 360 put at 36.96% and the 280 put at 36.41%, a 0.55-point gap against 0.85 this morning, so the strikes converged. The honest statement is that spot is the first-order term with skew as a real second-order one, and roughly $140 per dollar is a usable approximation that should still be repriced on the day. Not an argument for urgency in either direction - the rail has been open for weeks and Gabriel sets the timing. Only the 5x 280P leg is reachable by this order; the 8x 300P leg has no written repair. 15 minutes to the close as this is written.
- resolved the real-time quote endpoint is back.
get_price_snapshot failed all nine attempts across roughly fifteen minutes of this morning's run and was reported as unavailable for the whole of it. It answered all fifteen calls this run, first try, with no retries needed: thirteen equities, the GOOGL Dec-28 340 put, and one repeat. Every equity came back top_status REALTIME with an unhalted last-trade stamp inside a 68-second window. The practical consequence is that this page's prices are read rather than reconstructed from five-minute bars and the positions feed, and the campaign implied vol is the broker's own field rather than a solved estimate. The outage lasted one run and left no residue.
- wrong yesterday's explanation of the patchy prior_close field does not survive today.
Wednesday midday's page concluded that prior_close service rate 'is a function of the time of day, not of the feed's health', on the evidence that the morning served 1 of 13 and the midday run seven hours later served 5 of 13. Today's midday run - the same slot, the same thirteen contracts, the same broker - served 1 of 13, EQT alone. Two observations at the same time of day differing by a factor of five is not a clock effect. What does hold, and is the part worth keeping, is the underlying finding: a low service rate is not evidence of a degraded feed. The twelve unserved names were derived as last minus the broker's own change field and ten of the twelve reproduce this morning's independently sourced daily-bar closes to the cent. The time-of-day story should not be carried forward.
- wrong this morning's trailing-slash diagnosis of the page URL does not reproduce.
This morning's page corrected Wednesday's Cloudflare-edge-cache explanation and replaced it with a trailing-slash one: that markets.dottl.xyz/2026-09-10 serves the right page at 40,573 bytes while markets.dottl.xyz/2026-09-10/ serves the 6,675-byte site index. Tested against this run's deploy, the behaviour is the reverse and simpler than either story. The no-slash form returns an HTTP 308 with location /2026-09-10/ and a zero-byte body; the trailing-slash form returns 200 and the 28,366-byte page. That is Cloudflare Pages' ordinary directory redirect, which every browser follows, so both forms land a reader on the right page and neither is broken. What both this morning's note and Wednesday's were actually looking at is curl without -L reporting the redirect as an empty response. Neither an edge cache nor a slash convention is involved. The link below is the no-slash form the prompt specifies, and it resolves.
- found this run the solved-IV method reads about a vol point high, and the bias is not constant.
This morning's run could not read implied vol from the broker and solved it instead off the GOOGL Dec-28 340 put's own mark, disclosing a measured bias of +0.68 vol points from a single back-test on the prior day. Today both numbers exist on the same leg at the same moment: the broker's option-midpoint-iv reads 35.74% and the same solve run on the same mark returns 36.68%, a bias of +0.94 points. Larger than the disclosed estimate and in the same direction. Nothing here changes a verdict - the nearest IV trigger is 7.3 points away, roughly eight times the error - but the per-leg vols quoted in this run's action item are solved values and are comparable to each other, not to the broker's 35.74%.
- carried the midday slot still fires 25 minutes before the close, not the hour it is written to fire.
Reported as new on Wednesday and unchanged since: the written slot is '12:00 PM Pacific (one hour before the close)', the cron entry is '35 6,12 * * *', and the book here was pulled at 12:35 Pacific with the bell at 13:00. It cost nothing again today - every quote is live and every number is a live number - but the runway before the close is 25 minutes rather than the 60 the prompt describes, which matters for anything Gabriel would want to send before the bell. Not changed here: the cron entry is written configuration.
- carried two account rails have still never been measured.
rails.py reports stressed_excess_liquidity and short_dec28_340p_extrinsic as unevaluated and this run treats neither as passing. The first needs IBKR Risk Navigator with the TWS gateway up and has never been measured. The second is different today: the script cannot evaluate it without a full Dec-2028 chain pull, but the specific leg it names was quoted live this run, and the runbook Part 4 sweep - which is a hand check, not the script - reads its extrinsic at $52.92 against a $5 trigger. That is reported in watch_level as a swept row, not as a rail the script cleared.