Skip to content

Core concepts

Rules: a line or a document ​

A rule is something your agency's work has to follow. In Vythos it has one of two homes:

  • A line you write in Vythos. Never say "cheap" in Northwind copy. Day rate is £850 for workshops. One statement, typed on the Playbook page, or saved from Claude or another AI tool and added by you.
  • A document you name. Your rate card in Google Drive, your tone of voice page in Notion, a signed PDF you uploaded. Vythos follows the file.

Each rule has exactly one home, and that home is the one place it's changed. A line is rewritten in Vythos; a document is edited where it lives. A rule never has two places to edit it, so it can never drift from itself.

A rule in one line ​

Most of what an agency follows was never written down: what a client said no to, a promise made on a call, the word everyone knows not to use. A line is the quickest way to put that where your AI tools will see it, with nothing to upload and no document to keep in step.

A one-line rule carries:

PartWhat it is
The lineOne statement, up to 400 characters. It's what your AI tools receive, word for word
CategoryOne of the seven categories. Vythos suggests one as you type; you can change it
ClientEveryone, or the client whose page you wrote it on
WhyOptional. The reason, so the next person knows whether it still holds
UntilOptional. An end date, for a promise or anything that lapses. After it, the rule is no longer sent
ValuesWhat the line itself states. A word in quotes in a never say line becomes a banned word that drafts are checked for. See Values

A line is never read by an AI model to decide what it means. The category suggestion and the checks below are plain word patterns, so they answer as you type and use no credits.

Two checks happen before a line is saved:

  • Something that sounds like it changes — "currently running TikTok ads", "this month's budget is…" — gets a question first, because your AI tools will treat it as true until someone changes it. You can rewrite it, or save it anyway.
  • The same line twice is refused, with where the first one is.

To change a line, rewrite it: the new wording is the next version, in force from that moment, and the old one is kept. See Update a rule.

A rule that is a document ​

Some rules already live in a document your team works from, and that document should stay the place they're changed. Naming it makes it a rule.

The rule points at the file, not at a copy ​

When you add a document, Vythos records which file it is — the Google Drive file ID, the Notion page ID, or the name of the file you uploaded. Not the folder path, not a copy.

So:

  • Renaming the file changes nothing. The rule still follows it.
  • Moving it to another folder changes nothing.
  • Editing it updates the rule — see Update a rule.
  • A different file is a different rule. Saving "Rate Card 2026" as a new file beside the old one doesn't update anything. Add the new file and tick replaces on the old one.

Vythos keeps the text it read ​

Vythos reads the document and keeps that text with the rule. It has to: an answer, a comparison or a draft check that had to open your Drive every time would be slow, and would break the moment the file was briefly unavailable.

  • Your original file never moves and is never stored as a file. Vythos holds the text, not the document.
  • The text is what a tool sees. Open a rule and you can read exactly what was taken from the file — tables included, formatting simplified.
  • If the file becomes unreadable, the rule keeps working from the text it last read, and says so.

How a document rule gets its name ​

From the document's first heading if it has one, otherwise from the file's own name. So a Google Doc starting with "Rate Card 2026" becomes a rule called Rate Card 2026, and a file called terms-of-business.pdf with no heading becomes Terms of business.

What Vythos does with the document ​

  1. Reads it with your access, at the moment you add it. If you can't open it, neither can Vythos, and it says so rather than adding an empty rule.
  2. Files it under the category you chose, for every client or one client.
  3. Reads any values it recognises — figures like payment terms or a day rate. You decide whether they're right. See Values.
  4. Watches it from then on: a light check about every ten minutes, and a proper read only when the document has actually changed.

Which to use ​

Use a line when…Use a document when…
It's one thing to follow: a word, a promise, a decision, who signs offIt's a whole policy: a rate card, terms of business, brand guidelines
It isn't written down anywhere yetYour team already edits it somewhere
It came up in the work — a correction, a client's noIt's long, or has tables the rule depends on

Both reach your AI tools the same way, ranked the same way. A client page shows both together.

Nothing becomes a rule without a person ​

Connect Google Drive and a hundred documents flow into memory. None of them becomes a rule. Upload a folder of contracts, ask a question, let an AI tool report an outcome — still no rules.

A rule exists because a person with the right access wrote it, named a document, or added what an AI tool proposed. An AI tool can propose a line when you ask it to — "save this to the Playbook" — but the proposal waits for you in Vythos, and nothing changes until you add it. See Save from your AI tools.

Why it works this way

Software can guess which documents look like rules, and an AI can be talked into "remembering" anything it reads. Neither can know what your agency actually stands behind — and a governance layer that guesses wrong is worse than none, because everything downstream inherits the mistake with full confidence. So Vythos doesn't guess. One click by the person who knows is both faster and correct.

What can be a rule ​

SourceCan be a ruleNotes
A line you write on the PlaybookYes
A line an AI tool proposedOnce you add itIt waits under Waiting for you until then
Google Drive fileYesIncluding Google Docs, Sheets and Slides
Notion pageYes
A file you uploadYesUpload it first, then add it from Local files
Website, GitHub, GmailNoThese feed memory only. Write what matters as a line
An outcome an AI tool reportedNoAgent output is evidence, never governance

Readable formats are listed in File formats. A folder is not a document: pick the file inside it.

Next: Categories.

Vythos — the context layer for agencies that run on their own rules.