Seven Date Fields Failed This Morning. Four of the Events They Describe Fire Before Tonight.
We set out to build an event map for the rest of today — US CPI at 13:30 UTC, the New York option cut at 15:00, a Dallas Fed speech, and a 42 billion dollar ten-year auction at 18:00 — and instead found seven date or time fields that are wrong, missing, stale or contradictory, four of them attached to events that fire before tonight. Three dated expiry routes all returned client errors at the correct slot, which kills yesterday's "wrong slot" explanation and makes this the fifth session running with no board; we say plainly that we do not know where the optionality sits and refuse to invent a pin. One calendar lists the ten-year auction with a 5.30% prior yield while the cash ten-year trades near 4.86 — 42.0 basis points away, and 2.0 from Monday's thirty-year close, which is a reconciliation hypothesis and not a conviction. Logan is still 14:35 or 15:50, now two-to-one toward the later time but on forward calendars, which are statements of intent rather than reaction notes, so a 14:30 to 16:00 blackout is the only setting correct under both. A live blog puts a 13:30 release at 09:00. A search-topping auction record is a 12 May page with no date on it anywhere, which is why the date check fails where the level check works. And a syndicated article whose slug encodes 10 November 06:49 carries metadata saying 9 November 22:49 — eight hours apart, on the publisher whose slug we have treated as a timestamp for eight years. That is not a wrong number; it is a rule with a dependency we had not checked.