Heartbeats & Schedulingintermediatecurrenttested against paperclip 0.9
Heartbeat basics for beginners
Heartbeats should match the speed of the work. Faster is not automatically better.
Treat heartbeats as cost knobs
Every wake-up has a price. If nothing meaningful can happen every minute, do not schedule every minute.
Match cadence to task type
Examples:
- support triage: frequent
- daily content pipeline: scheduled blocks
- repo maintenance: a few times a day
Start slow
A slower heartbeat with clean logs is better than a fast heartbeat you do not understand.
Once the flow is reliable, tighten the cadence only where the user experience actually benefits.