Concepts
Eight words do most of the work on YAMO, and they mean specific things. A Playbook is a method written down. A Play is one step in it. A Service is the thing someone runs. Get those three straight and the rest follows.
Each page below answers one question on its own, so you can arrive at any of them without having read the others. For the one-sentence version of any of them, see the glossary.
- 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.
- What is a Runtime Instance?An Instance is one customer working relationship with a Service: their settings, their files, their connected tools and every run they have made so far.
- 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.
- 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.