Run
A run is one execution of a Playbook: YAMO carries out the steps with your tools and your data, on demand or on a cadence, and shows you exactly what it did. It is queued, then running. If a step asks for your approval it waits. Then it has either completed or failed, and there is no third ending.
Every run keeps its evidence, and every run carries a receipt. A run of your own Service is itemised, with the model cost and the platform operations as separate lines. A run of somebody else’s published Service shows the price you agreed and nothing else.
- Intake: what a run asks you forHow a run collects what it needs: the input contract, the difference between what is asked every time and what is set once, and what a missing answer does.
- Triggers: what starts a runThe four ways a run begins on YAMO: someone confirms it, a schedule fires, an approved agent calls it, or an approved run picks up where it paused.
- Schedules: running on a cadenceHow a Playbook carries a cadence, what a scheduled run does differently, how to pause one, and the honest state of changing a cadence today.
- Approvals: reviewing a step’s outputThe current operator gate pauses after a step runs. Learn what it holds, what approval means, and which decision controls are still unavailable.
- Outcomes and Run recordsRead a Run’s delivered Outcome, available evidence and receipt. Learn how owner and customer views differ, and how to copy or download the work.
- Delivery: where the outcome landsFind finished work in the Instance and follow email notifications. Learn when an email includes the Outcome, when it links to it, and current limits.