Routines

Routines are matic's scheduling primitive: markdown files with YAML frontmatter that fire on a cadence to emit a Signal into the work lifecycle. They sit alongside channels, callbacks, and webhooks as a Signal source, available at every scope (org, project, team, agent) and distinct from Subscriptions in that firing is deterministic and time-driven rather than reasoning-driven. Use them to schedule recurring business processes, register post-delivery observability, and drive the Observe → Hypothesize → Evolve loop that lets agents improve their own operation.

Routine Format

The on-disk shape of a routine: frontmatter fields for scope, emitted signal type, target metadata, firing conditions, payload intent, and enablement flags. Learn more →

Schedule and Cron

How cadence is declared — cron syntax, natural-language expressions, timezones, and timing windows that determine when a routine is eligible to fire. Learn more →

Callbacks

Precompiled, deterministic executables registered against a Signal event so work planned in advance runs without GenAI inference — the counterpart to Subscriptions. Learn more →

Eval Routines

The built-in routine.eval fired by the daemon scheduler to drive an agent into Assessment after first engagement, after HITL escalations, and on the cadence set by org Policy. Learn more →

Missed Fires

What happens when a routine fires but its Signal can't be processed — Dead Letter Queue handling, missed_fire events, retry policies, and alert thresholds that surface to the Feed. Learn more →

Observe, Hypothesize, Evolve

The continuous-improvement loop routines enable post-delivery: monitoring routines observe regressions, agents form hypotheses from accumulated Experience, and confirmed hypotheses evolve into new Work Items, Routines, Policies, or Skills. Learn more →