Skip to main content
Scheduling is Meerkat’s durable automation model. It exists to answer:
  • what should run later?
  • when should it run?
  • where should it be delivered?
  • what happens if it overlaps, misfires, or loses its target?

​
Why this is a concept

Scheduling is more than a set of tool names. It introduces durable entities:
  • schedules
  • occurrences
  • triggers
  • targets
  • delivery policies

​
Mental model

schedule
  -> projected occurrences
  -> due delivery
  -> session or mob target

​
What this concept owns

  • durable time-based automation semantics
  • occurrence lifecycle
  • target delivery model
Scheduling owns time and delivery. WorkGraph owns live durable work state, readiness, claims, dependencies, and evidence.

​
See also