Site maintenance
Daily, around 08:00 Europe/London
From 16 September 2026
Checks the site, fixes useful small problems and reviews pending work. Changes pass review and publication checks.
Maintenance record →The machinery, with receipts
What we schedule, what actually ran and what changed. Maintenance, Feral and evidence reviews are now scheduled in the cloud. The old Linux bot host is switched off.
Configuration confirmed on . The three editorial tasks run in Codex cloud, with start times that may vary by up to an hour. Scheduled work is recorded only after it runs.
Daily, around 08:00 Europe/London
From 16 September 2026
Checks the site, fixes useful small problems and reviews pending work. Changes pass review and publication checks.
Maintenance record →Tuesday and Friday, around 15:00 Europe/London
From 18 September 2026
One bounded council cycle. New experiments must pass critique and publication checks before they appear.
Feral ledger →Monday, around 15:00 Europe/London
From 21 September 2026
Reviews our five predictions against primary evidence, checks model records and considers useful prompt and tool updates.
Our predictions →Daily at 05:30 UTC
Existing GitHub Actions schedule
Checks tracked prices against the public provider catalogue. Validated changes are published with their actual check dates.
Price-check runs →Completed work appears in the maintenance record, Feral ledger and GitHub checks. The historical bot log below remains separate. News and Radar stay as archives.
Window ending 22 Sept 2026, 10:15 UTC. Counts cover price checks and historical bot records present in this build.
recorded runs
successful results
recorded API cost (USD)
Cost data exists for 8 of 8 runs. It excludes hosting and unlogged activity.
Price snapshots remain active in GitHub Actions. The six Python content timers below are inactive. Their former schedules and actual run records are preserved.
Previously generated daily digests from five RSS feeds. The news section remains a historical archive.
Former schedule: daily at 07:00 Europe/London
Last recorded: · success ·
The inactive writer can propose sourced editorial drafts from RSS reporting. Drafts stay unpublished until their claims are reviewed.
Former schedule: daily at 08:00 Europe/London
Last recorded: · success ·
Previously generated product-launch picks from RSS feeds and Hacker News. The Radar remains a historical archive.
Former schedule: daily at 09:30 Europe/London
Last recorded: · success ·
The inactive writer can propose an unpublished discovery for review. Its link checker records reachability and does not promote drafts.
Former schedule: Sunday at 10:00 Europe/London
Last recorded · verify: · success ·
The inactive writer can propose two unpublished prompt drafts. Reviewed recipes are maintained through the current editorial schedule.
Former schedule: Wednesday at 09:00 Europe/London
Last recorded: · success ·
Checks the tracked model IDs against OpenRouter's public price catalogue in GitHub Actions. Changed data passes validation and a site build before publication. No paid model call.
Daily at 05:30 UTC in GitHub Actions
Last recorded · prices: · success ·
The inactive bot proposed updates to the earlier Horizon lanes. Our five current predictions are assessed through the new evidence-review schedule.
Former schedule: daily at 10:00 Europe/London
Last recorded: · success ·
Up to 100 recent records across 14 dates. Times and dates are UTC. Outputs may be posts, model updates or proposals.
The model price job reads OpenRouter's public catalogue in GitHub Actions. It calls no AI model. Large price changes and locked fields are held for review, and missing quotes stay unknown. It publishes the validated data commit, then deploys the site already built from that data.
Cloud maintenance works through reviewed changes and GitHub publication checks. Evidence reviews can revise a prediction when the sources justify it. They preserve the original call and explain the change.
The old Python timers are stopped with their Linux host. Their recorded runs and costs remain available here. A configured schedule is a plan, while a dated execution record tells us what actually happened.
Price-check workflow · Historical bot source · Inspect the raw log