- found this run the smoothed GPU series is measurably quieter than the daily one, and this morning's '$1.99 floor' was not a floor.
This morning's page argued the fix for the noisy daily series already sits in the three-hourly captures, and pointed at eight consecutive captures printing $1.99 or $2.00 as evidence. Two captures have landed since it was written: $2.27 at 08:07 and $1.89 at 11:07, up 14 percent then down 17 percent, on a day with no US market open and no news. So the streak was not a floor and should not have been read as one. The smoothing argument itself is unharmed and now carries a number. Computed over the whole record from gpu-spot-intraday.csv against gpu-spot-daily.csv: the daily median has a coefficient of variation of 21.1 percent, ranges $1.84 to $4.01, and moves 20 percent or more day over day on 9 of 19 transitions. The 24-hour average across days with at least four captures has a coefficient of variation of 11.4 percent, ranges $1.93 to $2.94, and moves 20 percent or more on 1 of 18 transitions, with zero falls of 20 percent or more anywhere in the record. Median day-over-day move is 6.3 percent smoothed against 16.3 percent raw. That is the whole case in one line: on the smoothed series a 20 percent fall would be an event, and on the raw series it is a Tuesday. Nothing changed - the tripwire's definition is a written rule and this check does not rewrite written rules to fit the instrument.
- found this run the intraday series inherits the same missing history, so smoothing does not shorten the wait.
gpu-spot-intraday.csv starts 2026-08-19, one day after the daily series. Moving the tripwire onto the 24-hour average would make the threshold meaningful but would not make it evaluable any sooner: the 90-day lookback is starved on both series until roughly 2026-11-16 either way. Worth stating plainly so the two problems are not confused - one is a measurement problem that a better statistic fixes today, the other is a history problem that only time fixes.
- will happen again the cron has no trading-day guard - six runs against one session.
The schedule is '35 6,12 * * *' with no timezone anchor and no market-calendar test. Saturday twice, Sunday twice, Labor Day twice: six runs, all against Friday 2026-09-04's single finished session. Five of the six could only confirm the first. Reported since 09-05 and unchanged, because the cron is Gabriel's to edit.
- will happen again deploy.sh still needs an arm64 node pinned ahead of it on PATH.
/usr/local/bin/node is a Mach-O x86_64 binary and sits ahead of /opt/homebrew/bin, while wrangler's cached workerd is darwin-arm64 only. Worked around per-run again with PATH=/opt/homebrew/bin:$PATH, for a fourth consecutive run. Still not fixed inside deploy.sh.
- will happen again markets.dottl.xyz has no Access gate.
An unauthenticated request from this machine returns the full page - NLV, every position, every strike and every quantity - to anyone with the URL. book-check.dottl.xyz is gated behind Cloudflare Access; this one never has been. Not changed unilaterally: gating it is a call about who you want to be able to open the link.