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.
A Playbook declares the tools it needs. Those declarations are Connectors, and they are part of the definition: they travel with the Playbook whoever runs it.
A Connection is the other half. It is the authorisation a person gives so that a run can actually reach one of those tools on their behalf. Two words, two things, and posts under this topic are careful about which is which.
What a run can reach
Only what a Connection allows, and only for the run that needs it.
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.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.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.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.