
Everything Joymore enforces comes from documents you can read and edit. No rule builders, no configuration screens. It all lives on the Knowledge page.
A checklist is your compliance rulebook, written as plain task items under section headings. Each item becomes a check in every review, and every issue quotes the exact line it enforced, so the rules are always yours, in your words.
Each checklist's Applies to scope (state, transaction kind, side, property type, financing) decides which files it governs; assignment is automatic. Edit the checklist and every matching file follows the new rules.
A playbook is anything you want the agent to know or do: office procedures, tone for emails, when to escalate to a human. Playbooks shape the agent's everyday judgment.
Creating either one starts a chat: Joymore interviews you and drafts the document, and you refine it. When the agent later suggests changes, they appear as tracked edits you accept or reject.
Upload your brokerage's PDF forms and Joymore catalogs them automatically (fields, page count, revision) so reviews know exactly which form a document is and what should be filled in on it. Standard state forms come from plugins (see Connecting apps).

Automations run the agent on a trigger instead of a request: on a schedule (like weekday mornings), when a transaction enters a stage (like going under contract), or manually. Describe the job in plain language, like "list transactions closing within 10 days that still have failing checks", and Joymore sets it up, tells you if anything is missing before it can activate, and keeps a run history you can inspect.
