Schedules: running on a cadence

Some work is worth doing on a rhythm rather than on request: a Monday morning digest, a weekly market watch. A Playbook can carry a cadence in its own document, and when it does, YAMO runs it on that cadence without anyone present.

Where a cadence comes from

It is part of the Playbook, declared alongside the trigger. A Playbook whose trigger is a schedule and whose document names a cadence is registered to run on it; a Playbook that names one but is set to run manually is not. Both halves have to agree, which is checked when the Playbook is deployed.

Two of the templates in the library ship with one. The Meeting Week Digest runs Monday mornings; the Weekly Market Monitor runs a little later on the same day.

What you can do with it today

You can pause a schedule and resume it, from the Playbook's Schedule settings. The current cadence is shown there in plain words rather than as a cron expression.

You cannot currently set or change a cadence from the product. A Playbook runs on the cadence its definition shipped with, or on none. Editing it is not one of the fields the builder exposes, and there is no cadence picker. If you need a different rhythm, that is a change to the Playbook's own document.

We would rather write that down than leave you looking for a control that does not exist.

What a scheduled run does differently

Nothing, and that is the point. A scheduled run is subject to the same readiness checks, the same charging, and the same approval gates as one you started yourself. It uses the input defaults, which is why setting them is part of the setup rather than an afterthought. And it produces the same run folder and the same receipt.

A schedule belongs to the Instance rather than to the Playbook, so pausing yours does not affect anybody else running the same method.