Evergreen without the spam: cooldown floors and weighted rotation
Evergreen publishing is easy to build badly: put posts in a bag, draw one, post it, put it back. Do that for a month and your audience sees the same content on a suspiciously regular cadence — the exact pattern that reads as automation to both humans and platform classifiers.
Weighted, not round-robin
Each slot in the pool carries a weight. When the scheduler picks the next evergreen post it draws proportional to weight — your proven performers recur more often, but they're competing in a lottery, not a queue. Two high-weight slots can't monopolize the rotation because cooldowns still apply.
Cooldowns with a floor
After a slot publishes, it goes on cooldown — and the minimum cooldown is a product guardrail (on the order of a week), not a user setting you can tune to zero. The pool can pause, the slot can be disabled, but nobody can make 'the same post every day' happen by accident.
What the API sees
Agents interact with the pool like any other surface: GET /api/v1/evergreen returns slots with weight, publishCount, and cooldownUntil. A monitoring agent can watch the pool's health; it cannot override the cooldown floor — that rule lives below the API.