What is a Run?
A Run is one execution of a Playbook inside an Instance, from whatever started it to the finished artifact. It is the unit YAMO meters and charges for.
On this page
A Run on YAMO is one execution of a Playbook: one occasion on which the steps were carried out, from whatever started it to the finished piece of work it produced. It happens inside a Runtime Instance, which is where the answers, the files and the history live.
A Run is also the unit YAMO meters. Everything on your receipt is attributed to a run, and a run you did not make costs you nothing.
What one Run records
A Run is designed to be explainable afterwards, so it keeps more than its result.
- What started it, and who. A person confirming it, a schedule, or an external agent calling it.
- A snapshot of the definition it ran. So a run stays coherent even after the Playbook is edited. A run that pauses and resumes continues from its own snapshot rather than quietly switching to a newer version halfway through.
- What each step produced, in order, as its own document.
- The finished artifact, identified separately from the working documents.
- Its receipt.
That is what the run folder shows you: the inputs it was given, each stage's work in sequence, and what it cost. What you see is what ran.
How a Run ends
A Run is queued, then running. If a step declares a human gate it becomes
awaiting_approval and waits. Then it is either succeeded or failed.
Those are the only endings. There is no partial state and no silent one: a failed run says which step it stopped at and why, and work that had already succeeded is kept rather than thrown away.
Run, or Instance?
A Run is one occasion. An Instance is the ongoing relationship that contains many of them. The long-lived customer context is the Instance; the Run is discrete, auditable and finished.
A Run is also not a Play. A Play is one step in the written method; a Run is one time the whole method was carried out.
A real one
Running URL SEO Audit means giving it one URL and confirming. The run executes two Plays: research, then write. It produces the research notes as a stage document and the prioritised audit as the deliverable, and both stay in the run folder afterwards, alongside the receipt.
What to read next
- What is a Runtime Instance? for where runs live.
- Run for the one-sentence version.
- Run for triggers, schedules, approvals and delivery.
More in Concepts
Related
What is a Connector?
A Connector is a tool a Playbook says it needs in order to do its work. It is a requirement written in the document, not an account or a password.What is a Connection?
A Connection is the access you have authorised, which is what turns a tool a Playbook asks for into a tool a run can actually reach on your behalf.What is a Reference file?
A Reference file is a document a Playbook reads while it works: your house style, your offer, your watchlist. They live together in your Knowledge Vault.What is a Playbook?
A Playbook is a way of working written down as a document that software can follow: the steps, the tools they may use and the knowledge they read.What is a Play?
A Play is one numbered step inside a Playbook. It says what that step does, what it reads, what it hands on, and which tools it is allowed to call.What is a Service?
A Service is the thing other people can buy and run. It exists from the moment you start making it, and passes through three stages before anyone sees it.Pricing
How YAMO charges: you pay for the runs you make, and nothing for the ones you do not. What a run is, what it includes, and what publishing costs.Who it's for
The six kinds of expert YAMO is built for, and what changes when the method you already follow becomes a Service that somebody else can run.
Open a Playbook that does this
Every template in the library publishes its contract and a real example output.