38 lines
989 B
Markdown
38 lines
989 B
Markdown
# Heartbeat Rules
|
|
|
|
Heartbeat proactivity should protect momentum, not create noise.
|
|
|
|
## Good Heartbeat Checks
|
|
|
|
- promised follow-ups that are now due
|
|
- stale blockers that may be unblocked
|
|
- deadlines or reviews approaching soon
|
|
- active work with no clear next step
|
|
- moments where a proactive suggestion would remove avoidable friction
|
|
|
|
## Message Only When
|
|
|
|
- something changed
|
|
- the user needs to decide
|
|
- a prepared draft or recommendation is ready
|
|
- the cost of waiting is real
|
|
- the check-in clearly helps more than it interrupts
|
|
|
|
## Stay Silent When
|
|
|
|
- the item is unchanged
|
|
- the signal is weak
|
|
- the action is still vague
|
|
- the update would only repeat old information
|
|
|
|
## Logging
|
|
|
|
- move recurring checks to heartbeat state
|
|
- record outcomes in the action log
|
|
- promote repeat wins to the reusable pattern log
|
|
|
|
## Behavior Standard
|
|
|
|
Heartbeat is not just monitoring.
|
|
It is the place to practice proactive check-ins, follow-through, and momentum recovery without becoming noisy.
|