Glossary
One word for one thing. These six are the ladder YAMO is built on, in the order they build on each other rather than in alphabetical order.
- Playbook
- A Playbook is the method an expert captures — how a piece of work gets done, written down as a document the YAMO runtime follows exactly.
- Play
- A Play is one step inside a Playbook: a single named job, with what it reads, what it does and what it hands to the step after it.
- Service
- A Service is the thing that gets run. It exists from the moment its definition is created, as a Draft Service; Deploy makes it runnable and Publish makes it public.
- Instance
- An Instance is one customer's ongoing context against a Service: their setup, their connected tools, their files and their run history, held apart from everyone else's.
- Run
- A Run is one execution of a Playbook, from what started it to the artifact it returns. It is the unit YAMO meters, receipts and charges for.
- Connector
- A Connector is a tool a Playbook declares it needs. Authorising one creates a Connection — the binding that lets a run actually reach that tool on your behalf.
- Connection
- A Connection is access you have authorised. It is what turns a Connector, which is a requirement written in a Playbook, into a tool a run can actually reach.
- Reference file
- A Reference file is a document a Playbook reads while it works. Your reference files live together in your Knowledge Vault, which is the container they sit in.