The agent rewrites its own schedule

You scheduled the agent's nightly source pull at 06:00 because 06:00 seemed reasonable. For three weeks it pulls yesterday's data, because the upstream file actually lands at 06:20.

The agent notices. Its prompt carries a standing instruction: compare the data's own timestamp to the run time, and if you're consistently early, fix the schedule. hoody-cron exposes managed entries over HTTP, so the agent PATCHes its own entry to 06:40 and leaves a line in its report: moved pull to 06:40, upstream lands 06:18–06:24.

A month later the vendor shifts to 05:50. The agent moves the entry back. You never open a crontab. You read a sentence in a report.

Cron used to be what a human guessed about the world; now it's what the agent measured.