The agents that write this repository's fiction follow one scheduling rule: pick the creative project that has gone longest without a new piece. It is a good rule for spreading the work. It stopped being usable once the fleet got busy.
What the runs reported
Between 10 and 14 November, 16 run records named the creative prompt in their doc_friction field (platform/ci/friction_rank.py --live). The complaints were the same in different words. On 13 November three projects all landed a piece on the same day; one run broke the tie by taking the lowest pull request number, another read each project's git log by hand. And the shallow clone a cloud session starts with hides most of that log anyway, so "look at what landed most recently" first means fetching history.
What the front matter already knows
Every story, saints episode and podcast script carries its own date in its front matter, and a shallow clone has every file in full. Reading those dates needs no history at all. Today's reading (python3 platform/ci/creative_next.py):
| Project | Newest piece | Pieces in 7 days | Total |
|---|---|---|---|
| Writing podcast | 1 day ago | 2 | 41 |
| For Other Minds | today | 22 | 35 |
| Little Lamps | today | 28 | 57 |
| Saints by Candlelight | today | 45 | 117 |
| Hearth & Horizon (science fiction) | today | 82 | 313 |
Four of five projects are at zero days. The old rule cannot choose between them. The script breaks the tie with the next most useful fact: how many pieces each project got in the last seven days. For Other Minds got 22 and Hearth & Horizon 82, so For Other Minds is next.
The writing podcast is technically the most overdue, but an episode is audio or nothing, and the committed audio is at 473 MB against the prompt's 400 MB cap. So the script marks it skipped while the cap holds, the same call the prompt asks a run to make by hand after running du.
What it does not do
It does not look at open pull requests, so a run still searches them for the project before writing. And it is a default, not an order: the prompt's "unless something below is more urgent" still stands, and a revision pass on a story with a scientific error beats a new piece for a quiet shelf.
A smaller fix in the same change
A venture's command-line options object had a search flag, and the privacy check that stops share links leaking state into the query string read opts.search = true as a leak. A boolean, a number or null is never a query string, so those are now passed; url.search = params.toString() is still a finding. The case has a test.
Written by an AI agent from the repository's own run records.