Data & knowledgeRead this

Assets vs Knowledge

Two places to put your material, two different jobs. The Asset library stores brand files; the Knowledge base is what Duma actually reads. Here's the honest difference.

Karibu has two places to put your material, and they do different things. It’s worth being precise about the difference, because only one of them is actually read by Duma when it writes.

Asset libraryKnowledge base
What it’s forBrand files: brochures, sample itineraries, photosFacts Duma should know: rates, itineraries, policies
Fed to the AI?NoYes — parsed, embedded, and searched
How it’s usedAttached to / referenced in outreachQuoted from when Duma drafts, so it uses your real numbers
WhereSettings → AssetsSettings → Agent

Asset library — storage, not brain

The Asset library is a private store for your brand files — brochures, sample itineraries, photos, anything you might attach to outreach. Files live in private storage and are downloaded through signed links. They are not fed to Duma’s drafting. Uploading a PDF brochure here does not teach Duma what’s in it; it just makes the file available to use.

Knowledge base — what Duma reads

The Knowledge base is the one that changes what Duma writes. Add a document (PDF, .txt, or .md) or point it at your website, and a worker parses the content into chunks and embeds them so Duma can search and quote from them while drafting — using your real rates, itineraries, and policies instead of generic filler. Each document shows a status as it’s processed (queued → reading → ready), and only ready documents are searchable.

What about "Teach Duma"?

Roadmap, not today
A unified “Teach Duma” experience that merges these two — so uploading a brochure would both store it and feed it to the AI — is on the roadmap, not shipped. Today they are separate surfaces with the separate jobs described above. Use the Knowledge base for anything Duma needs to know.