Docs
A Playbook is how you do your best work, written down. YAMO follows it exactly, every time: your data, your tools, your say-so. These pages cover the three things you do here, in the order most people meet them: Run, Build, Publish, with the real templates from the Playbook Library as worked examples.
If you arrived wanting one word defined rather than a system explained, start with Concepts. What changed and when is on the changelog.
- ConceptsThe words YAMO uses, defined one to a page: Playbook, Play, Service, Instance, Run, Connector, Connection and Reference file, and how each relates.
- RunWhat happens when a Playbook is carried out: what a run asks you for, what starts one, what it produces, and how the finished work reaches you.
- BuildMaking a Playbook: starting from a template or from a description of the work, writing the steps, and getting it ready enough to deploy and run.
- PublishPutting a Service on your Front Office: what the listing asks for, what has to be true before you can publish, how it is priced, and how you get paid.
- ConnectorsThe tools a Playbook calls to do its work: how one is declared, how you authorise it, whose access satisfies it, and what a run does when it is missing.
- ReferenceThe exact contracts: what a playbook.md, a Play file and a SKILL.md may declare, the one programmatic endpoint, and the limits a run actually meets.
- Getting startedFrom a template to your first finished run: copy a Playbook into your account, fill in what it asks you for, run it, and read what comes back.
- Reference filesYour knowledge layer: account references every Playbook can read, Playbook references scoped to one method, and placeholders for what is missing.