Theme
Core concepts
The Playbook
The Playbook is what your agency's work has to follow, for everyone and for each client. Each entry is a rule: a line someone wrote, or a document someone named and said "this one counts". See Rules: a line or a document.
Everything else Vythos holds — briefs, notes, emails, finished work — is memory. Memory is searched. The Playbook governs.
What's on the page
A rail on the left. Everyone comes first: your house rules, for every client. Below it, each client you've added, with a count of their own rules, and a + to add a client. At the bottom, Recent changes. Each page has its own address, so a client's page can be linked and the back button works.
Everyone's page holds the house rules, under the seven categories. Each category shows the line saying what belongs there, and a category with nothing in it yet is listed at the bottom.
A client's page answers "what does the AI know about this client?" in full:
- About {client} at the top — what's true about them, such as what they sell, who to and who they compete with. Your AI tools read it as context, not as a rule.
- Their own rules, under the same categories.
- Everyone's rules that apply to them, folded into the same categories and marked Everyone, with a switch to hide them.
- For a new client, three questions to start with: What do we say no to?, Who signs off? and What have we promised?. Each answer becomes a rule.
One box on each page adds a rule, or on a client's page a fact. It shows what the line will be as you type. See Add a rule.
Waiting for you appears on a page when an AI tool has proposed something for it that you can add. Nothing changes until someone adds it. What you suggested yourself is under Your suggestions. See Save from your AI tools.
What a rule shows
| On the row | What it means |
|---|---|
| The line, or the document's title | A one-line rule shows its sentence. A document rule shows the title from the document's first heading or the file's name |
| Never say chips | Words a Brand & voice rule bans, shown as chips |
| Since and Until | When a one-line rule started, and when it ends if it has an end date |
Version 2, or v2 | The rule has been changed: a one-line rule says Version 2, a document rule shows a v2 badge. Nothing means it's still at version 1 |
| Value chips | Figures the rule states — a day rate, payment terms. A green border means a person confirmed them; a plain border means Vythos read them from a document. See Values |
A one-line rule offers Rewrite this rule and Retire this rule on the row (on hover, and always on a touch screen). A document rule opens to show the document's full text as Vythos reads it, a line telling you exactly how to update that particular rule, a link to the file where it lives, and the option to retire it.
An orange note appears on a document rule whose file can no longer be read — it was deleted, or access was withdrawn. The rule keeps working; it just stops following the file until you fix it. See When a file can't be read.
Order matters
The Playbook is ordered, and the order is what your AI tools are given:
- A client's rules beat your house rules. Always. If Acme's contract says 45 days and your terms say 30, work for Acme is on 45.
- Within a scope, categories rank. Terms and commitments outrank pricing; pricing outranks process. Full order in Categories.
- Rules beat memory. A rule is current and governed. A meeting note is what someone said once. Where they disagree, Vythos answers from the rule and tells you the note disagrees, so you can go and fix the note.
Who can change it
Everyone in the workspace has the Playbook page, showing the clients they work on and the categories they can see. The workspace owner adds, rewrites and retires any rule, and adds what AI tools propose. A teammate with Can edit for a category does the same for that category, and whoever looks after a client does it for that client's rules, except pricing and terms. A teammate's AI tool can propose a rule or a fact; it waits for the owner.
Where you choose someone's access, the screen says which parts are active, so nobody is promised something the app doesn't do. See Your team and their access.
What a rule is made of
| Part | A one-line rule | A document rule |
|---|---|---|
| Its words | The line itself | The text read from the document, kept so Vythos can answer and compare without opening the file every time |
| Category | Suggested as you type; you choose | You choose it when adding the document |
| Client | Everyone, or the client's page it was written on | Every client, or one client you picked |
| Values | What the line states, confirmed by you | Figures Vythos read from the text, which you can confirm |
| Why and until | Optional | — |
| Version | 1 when added; +1 each time it's rewritten | 1 when added; +1 each time the document's wording changes |
| History | Every past version, kept — nothing is deleted | The same |
The one-document rule
One document makes one rule. File the same document under a second category and the first reading stands down rather than joining it, so a document can never be two competing rules at once.
That constraint is worth designing around: if a file covers both your pricing and your process, splitting it into two documents gives you two rules you can update, replace and retire independently. The same goes for a line: one statement, one rule.
Next: Rules: a line or a document.
