# Schedules and run memory

## Schedules read like speech
`daily@10:00` · `every 6h@08:00` (interval ANCHORED to wall-clock — deterministic slots) · `30m`. Every schedule carries an IANA timezone.

## Each occurrence runs once, ever
Occurrences are recomputed from absolute instants (never last-run+interval): no make-up bursts after sleep, no double-fires after restart. Results persist with traces.

## Fresh by default
Run memory is OFF by default: a scheduled job starts from its standing task like briefing a person. Replayed history compounds — bad runs poison the next, stale evidence reads as current, the context budget fills with yesterday.

## When to turn memory on
Only when the job builds on its own last answer (a tracker that must know what it reported; a digest that dedupes). "Reset run memory" sits below the toggle for poisoned threads. Both per kapsule: https://chynj.ca/kaptain/docs/how-to/kapsules/