🤖 Generated by the Daily AI Engineer
Evidence
AGENTS.md (Cadence & focus, line ~1704) opens:
Dispatched hourly (the deployment loader owns the exact cadence) — that is the interval between runs, not a per-run time budget.
The registered Claude Code task is cron 0 */2 * * * — every 2 hours, at even hours (confirmed via the scheduled-tasks listing, 2026-07-19). The parenthetical does defer to the loader, so this is not flatly wrong, but the headline number is stale and other passages compound it (e.g. "across hourly runs older PRs accumulate…").
A third variant existed in the loader itself until this tick: daily-ai-assistant/SKILL.md named cron 0 */4 * * * and a 4-hourly slot list. That one was corrected directly under routine-prompt stewardship (before → after recorded in native memory and the run report); the loader now reads even hours local — 00/02/04/…/22, cron 0 */2 * * *.
Impact
Cadence is load-bearing for pacing decisions: Latency discipline tells a run to overlap waits against the interval before the next tick, and Cadence & focus frames the interval as the between-run budget. An agent reading "hourly" under-estimates its slack by half, which biases it toward ending a run early rather than overlapping a long CI bake.
Expected behaviour
The constitution states a cadence consistent with what actually runs, or drops the number entirely and defers wholly to the loader (which is the more robust option, since the loader is the ground truth and the constitution cannot track a machine-local schedule change).
Acceptance criteria
Size: XS
Evidence
AGENTS.md(Cadence & focus, line ~1704) opens:The registered Claude Code task is
cron 0 */2 * * *— every 2 hours, at even hours (confirmed via the scheduled-tasks listing, 2026-07-19). The parenthetical does defer to the loader, so this is not flatly wrong, but the headline number is stale and other passages compound it (e.g. "across hourly runs older PRs accumulate…").A third variant existed in the loader itself until this tick:
daily-ai-assistant/SKILL.mdnamedcron 0 */4 * * *and a 4-hourly slot list. That one was corrected directly under routine-prompt stewardship (before → after recorded in native memory and the run report); the loader now readseven hours local — 00/02/04/…/22, cron 0 */2 * * *.Impact
Cadence is load-bearing for pacing decisions: Latency discipline tells a run to overlap waits against the interval before the next tick, and Cadence & focus frames the interval as the between-run budget. An agent reading "hourly" under-estimates its slack by half, which biases it toward ending a run early rather than overlapping a long CI bake.
Expected behaviour
The constitution states a cadence consistent with what actually runs, or drops the number entirely and defers wholly to the loader (which is the more robust option, since the loader is the ground truth and the constitution cannot track a machine-local schedule change).
Acceptance criteria
AGENTS.mdare reconciled with the same wording.Size: XS