Running services
What happens between a trigger and a finished artifact: intake, the ordered Plays, the approvals you keep, and the receipt at the end of a run.
A run starts with a trigger and ends with an artifact. Everything a customer experiences happens in between: what they are asked for, what the Plays do with it, where you keep an approval, and what the receipt says afterwards.
Posts under this topic are about that middle. They are written against the templates in the Playbook Library, so every claim has a worked example behind it.
The unit that is charged
A run is also the billable unit. What one run includes is its own post.
- The method is the assetAn expert who has delivered the same outcome enough times owns a method. Doing the work again by hand for every customer is what that method costs them.
- What one run includesA run is one execution of a Playbook, from the trigger that started it to the artifact it returns. It is also the unit that gets metered and receipted.
Other topics
Packaging expertise
Turning a method you already follow into a Playbook: what belongs in it, what a Play is, and how the finished thing stays yours to keep editing.Publishing and pricing
Publishing a Playbook so other people can pay to run it: the public contract a Service carries, who configures an Instance, and what is charged.Connectors and data
The tools a Playbook declares and the Connections that satisfy them: what a run can reach on your behalf, and what stays exactly where you put 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.