Skip to main content

​
Brains

A brain is the container for one company’s knowledge. Every document, folder, and tag belongs to exactly one brain. Your workspace is the account your teammates and billing belong to, and it contains exactly one brain — created when you first sign in and name your company. There is no brain switcher and no second brain to keep in sync. The same boundary applies to your agents. An agent can only reach the brain belonging to the account it connected as, and no tool lets it name a different one. Connecting an agent gives it your brain and nothing else.

​
Documents

A document is a title and a body, plus a few properties that make it findable later: The description deserves more attention than it looks like it needs. It is what an agent sees when it scans your brain for relevant context, and it is usually what decides whether the agent opens the document at all. A vague description is the most common reason good knowledge goes unused. Descriptions and tags are optional when you write in the app. They are required when an agent writes: anything an agent creates must arrive with a description and one to five tags. Agents are held to a higher standard than people here, deliberately — they are the ones producing volume. Documents also record where they came from. Every document is stamped with what wrote it, taken from the credential used, so an agent’s work is always attributed to that agent. It cannot be supplied, overridden, or faked by the writer. When you are reviewing your brain, you can always tell what a person wrote and what an agent did.
There is no draft, published, or archived state. Nothing is hidden from search because of where it sits in a lifecycle. A document either exists in your brain or it does not. The one flag that comes close is the lock, and it governs who may change a document, never who may see it.

​
Locked documents

A document can be locked. A locked document is approved, canonical content — an ideal customer profile, a brand guide, a privacy policy — and it refuses every change from agents and people alike until someone unlocks it: no edits, no retagging, no renaming, no moving, no deleting. Reading is untouched; it still appears in search, listings, and links like anything else. Locking is deliberately a human act. The document’s owner, or a workspace owner, turns the padlock in the document’s topbar. There is no agent tool for it, and there is no way around it: an agent that tries to change a locked document is refused, told who can unlock it, and told explicitly not to work around the lock by writing a copy somewhere else. This is the mechanism that lets you run agents at volume without your source of truth drifting. Lock what has been agreed; leave the rest open. Because a locked document is pinned in place, the folders above it are held too: a folder containing a locked document anywhere inside it cannot be renamed, moved, or deleted until that document is unlocked.

​
Extra properties

Beyond the standard properties, documents can carry others your own way of working needs: a review date, a customer name, a renewal quarter, a confidence level. They appear in the document’s properties and your agents can read and filter on them — “every customer document not reviewed since June” is a question a base can answer only because the review date is a property rather than a sentence buried in the text. Each extra property is defined once, in your brain’s field registry, with a name and a type. That is what keeps them worth having: an agent can only write a property that has been defined, so a brain never accumulates four spellings of the same idea. An agent can define a new one when it genuinely needs it, but it cannot invent an ad-hoc label on a single document and move on. Documents that arrive from elsewhere carrying properties nobody has defined still show them, and they surface in a review list where you can adopt or drop them — the same curation pattern as the tag registry.

​
What a document actually is

Every document in Tatara is stored as plain Markdown with structured properties attached — the same open foundation as Google Cloud’s Open Knowledge Format, the emerging standard for the context AI agents read. Two things follow from that, and they are the reason it is worth a paragraph:
  • Agents read it natively. Markdown is what language models are trained on and what they write best. Your knowledge does not have to be translated, scraped, or embedded into something else before an agent can use it — it is already in the shape agents want.
  • It is yours, in the open. Nothing is locked in a proprietary format. A board is not a special file type; a table is not a database row. It is all text you could read in any editor, search with any tool, or take somewhere else entirely.
You never have to write, read, or think about any of that. The app shows you documents, boards, tables, and maps; your agents handle the structure underneath. It matters only because it is the reason Tatara works the way it does — and the reason your knowledge outlives any decision we make about the product.

​
Titles and addresses

The title is the document’s identity, and its address follows from it. Rename a document and it moves; every link pointing at it is rewritten in the same operation, so nothing breaks and nothing has to be tidied up afterwards. A document’s address is its folder, then the document — product/pricing/pricing-page-spec — using simplified, URL-safe versions of each name. You see the full address in your browser’s address bar; everywhere else you see the real title. If a name is already taken in the same folder, Tatara adds a number rather than refusing or overwriting.
A title cannot contain /, #, |, [, or ], or a line break. Each of those means something in the way documents link to each other, so a title using one would produce links that could never resolve. Tatara refuses it up front rather than quietly mangling the name.

​
Folders

Folders group documents, and they nest up to twelve levels deep. Two folders in different places can share a name — a notes folder under product and another under marketing are different folders. What tells them apart is their full address. If you ask an agent to file something in “notes” and the name is ambiguous, it will ask you which one rather than guess. Documents link to each other, and Tatara tracks those links in both directions: every document knows what it points at and what points back at it. That backlink half is what turns a folder of notes into a brain — you open your pricing page and see every decision, playbook, and customer note that depends on it. To link to a document while you are writing, type its name inside double square brackets:
The link becomes clickable as soon as you finish typing it. To show different words, add a |: [[Pricing Page Spec|the spec]]. Your agents use the same links, plus a couple of longer forms for pointing at an exact address or embedding one document inside another. A link to a document you have not written yet is not an error. It is kept, shown dimmed, and connects itself the moment a document with that name appears. You can write toward a document that does not exist and let the graph close when you get to it — which is exactly how thinking actually goes. Deleting works the same way in reverse: links to a deleted document dim rather than disappear, and restoring it brings them back.

​
Tags and the taxonomy

Documents carry up to five tags. Separately, your brain keeps a tag registry that sorts every tag into one of three tiers: The three are independent, not a hierarchy. A topic does not belong to an area, and any goal can apply to a document in any area. A pricing page spec might be area product, topic pricing, goal acquisition — three separate answers, not one path through a tree. It means you can ask “everything about pricing” and “everything aimed at acquisition” and get useful answers to both.
The registry is advisory. Tags on documents are not checked against it, and coining a new tag never fails a write. A tag that is not registered turns up in a review queue on the tags page, where you can file it into a tier or merge it into an existing tag. Agents can coin tags freely and you curate afterwards, rather than agents stalling on a vocabulary they do not have.
The registry suggests one area, up to two topics, and up to two goals per document. That is guidance for you and your agents, not a rule the product enforces. The only hard limit is five tags. See Organizing with tags.

​
Deletion and recovery

Deleting is soft — Tatara keeps the content rather than destroying it, which is what makes recovery possible.
The web app has no trash and no undo. Nothing in it lists deleted documents or brings one back, so a delete made there is effectively permanent as far as the app is concerned.
Recovery runs through a connected agent: ask it to restore the document or folder. See Deleting documents and folders.

​
Where to go next

Document formats

Boards, trackers, tables, maps, and live views over your brain.

Connect an agent

Give your agent access, and put your brain to work.