Knowledge — the company's documents
Knowledge holds the documents that explain how your company works: the handbook, the agreements with a customer, the reason you do something the odd way. It is what the agent searches when you ask a question it cannot answer from records.
Three kinds of document
kyte has three kinds of document. They look alike — markdown, a title, some text — but they live in different places, and that decides who sees them and where you change them.
| lives | who sees it | where you change it | |
|---|---|---|---|
| A document in your folder | a markdown file in the folder you picked, on this computer | whoever can open that folder | in Knowledge, or in any editor |
| A note on a record | in the workspace, attached to a customer, a project, a task … | everyone who may see that record — teammates and the agent included | on the record |
| The company description | processes, roles and policies, in the workspace | everyone in the workspace | in the app it belongs to — a process in Processes |
A document in your folder
Point Knowledge at a folder and your documents are ordinary markdown files in it: editable in any editor, searchable by your operating system, backed up by whatever already backs that folder up. The subfolders are the tree on the left.
The file is the truth, and the only copy. kyte keeps nothing about it in the database, so nothing about it travels to your teammates or to an agent on a server: the folder is this computer's. If your team shares the folder — a network drive, a git repository — everyone sees the same files, because the folder is shared, not because kyte copied anything.
kyte watches the folder. A file you change in another editor, drop in from Finder or pull with git shows up at once. If the document you have open changes on disk while you are typing, kyte does not pick a side for you: it says so, and you choose Load the file or Keep mine.
There is no history for these documents in kyte. A folder that wants history is a git repository.
A note on a record
On any record — a customer, a project, a task — Knowledge → + New writes a note about that record. It lives in the workspace, not in a folder, so it reaches everyone who may see the record, including the agent on a server. It keeps a history like the record does.
The company description
How the company works, written down so people and agents can follow it: its processes, roles and policies. A process is one of these — you write and run it in Processes.
If the folder you picked is already your company's description repository (it holds a
company.yaml), its files are files like any other: you read, edit, rename and delete them in
Knowledge. kyte keeps what makes them a description — the api: line, the id, the owner — and
changes only the title and the text you typed. Want a review before a change counts? Keep the
folder in git and commit as usual.
Writing one
+ New for a document in the selected folder, with a title and a body in markdown. Opening a
document is editing it — there is no edit mode. Headings, lists, tables, [[links]] between
documents — the same subset the chat renders.
What the agent does with it
It reads them. "What did we agree with Northwind about invoicing?" searches the documents you may see and answers from them, naming where it found it. The agent on your computer reads your folder; an agent on a server sees the notes on records and the company description, never your folder.
It can also write one: "Write down what we just decided as a document in Knowledge". That is a write, so it is shown to you first.
What belongs here, and what does not
Knowledge is the company's library. A folder you hand the agent for one job is a workbench — see sharing a folder with the agent.
Rule of thumb: if a colleague would need it next year, it belongs here. If it is scaffolding for today's task, it does not. And if the whole team needs it, write it as a note on the record it is about, or keep the folder somewhere the team shares.