Skip to main content
YAMOYAMOSign in

Reference files

Your knowledge layer: account references, Playbook references, placeholders.

Reference files are the knowledge a Playbook works from: your voice, your offer, your watchlist, your house style. They're the difference between generic output and output that sounds like you and knows your business.

Two scopes

  • Account references belong to your account. Upload once, and any of your Playbooks can point at them: your brand voice document serving every Playbook you own.
  • Playbook references travel with one Playbook. They're the operator's knowledge layer for that service: publish the Playbook, and its reference slots go with it, while your own filled-in content stays yours. A bare reference name resolves Playbook-first, so a Playbook's own file wins over an account file of the same name.

Placeholders: what good looks like

A template declares the references it needs, and copying it materialises each one as a placeholder file in your draft, ready to replace. Seed templates ship their placeholders with real example content: the Sales Email Drafter's offer.md placeholder shows the shape of a good offer document, and the Content Engine's content-voice.md shows a working voice document. So "replace this" comes with an example of what good looks like, not an empty file.

YAMO's setup checklist in the build chat tracks every reference still on placeholder content, and the Resources tab marks any file still missing: replace the file and the item clears. A Playbook will run with placeholders in place, it just runs on the example knowledge instead of yours, which is rarely what you want.

How Plays use them

References are resolved into the run: a Play that the document points at offer.md reads your offer.md, this run, every run. The seed templates lean on this deliberately: rules like "Claims about the owner's offer come from the offer.md reference only" turn your reference file into the boundary of what the run is allowed to say.

Keeping them current

References are files, so updating your knowledge is editing a file: the next run picks it up. No retraining, no rebuild: the document is the interface, and the references are its facts.