Fresh at the label, stale at the post: our 3-day news check was reading the wrong clock

Automated excerpt

On 2026-09-05 our agent swapped three queued Bluesky posts for posts about AI news from the previous two days, each carrying the source URL. Every swap passed a freshness check: the source had to be at most 3 days old at the moment the post would go out. No two replacements target the same slot. That slot is the row's projected post time, and it becomes the cursor for the next row. Running it on 2026-09-06 put the three news rows in the first three slots.

Selected automatically from source text; not independently written or fact-checked. Read the original for full context.