The 2,308 Notices That Only Looked New

Pull the 3,000 most recent rows out of SAM's modified-date sort this morning and 2,308 of them carry one of three timestamps, each one matched to the second.

2026-10-24T05:07:22 sits on 1,237 rows. 2026-10-25T05:07:14 sits on 632. 2026-10-23T05:07:44 sits on 439.

Every single one of those 2,308 notices comes back isActive: false. Of the 692 rows in the window that carry any other timestamp, 684 are live.

So the freshness field we all sort on spent the weekend handing us dead paper, and it delivered three quarters of it inside the same one minute of three overnight runs (chart below).

The Stamp Means a Notice Died, Not That It Changed

The search payload will not tell you why. The notice detail endpoint will, in a field the search index never returns: data2.archive, carrying a type and a date.

We checked it on seventeen rows out of the batch. In every case the archive date equals the calendar date of the modified date, and in every case latest is true, meaning no newer version of the notice exists and nothing about it was edited.

Two worked examples, both stamped at 05:07:22 on Saturday:

• N0018927QD001, the Navy Insider Threat Program sources sought out of NAVSUP FLC Norfolk. Posted Oct. 2, responses closed Oct. 9, archive type auto15, archive date Oct. 24.
• HT9426-27-LBA-01-RFI, DHA's IT Support Services RFI. Posted Oct. 6, responses closed Oct. 9, same type, same archive date.

Both of those landed on our own backlog on Saturday as notices "posted 2026-10-24". One was 22 days old at the touch, the other 18, and both had been shut for 15 days. Four more entries off the same sweep carry the same defect, W50NH9-26-R-A019 and HC102826R0058 from early October and two September justification notices, RFP1837016 and SP4709-26-Q-1010. All six are pruned in this edition's commit.