Drive & Knowledge Base
Learn how Buda uses Drive as the source of truth for an Agent's private knowledge and file-grounded answers.
Drive & Knowledge Base
In Buda, an Agent's knowledge starts with its Drive. Drive is the private file workspace attached to an Agent, and it acts as the main source of truth for grounded answers.
What belongs in Drive
- Policies and SOPs
- Product manuals and FAQs
- Contracts and legal templates
- Research notes
- Portfolio or holdings files
- Project briefs and internal documentation
How Buda uses files
When a user asks a question, Buda does not rely only on the model's general knowledge. It can inspect relevant files in Drive, extract useful context, and answer based on your actual documents.
Why this matters
- Answers stay closer to your business reality
- Different Agents can keep different private knowledge bases
- Updating files is often easier than rewriting prompts
- Teams can audit what source material the Agent should rely on
Recommended file hygiene
- Keep folder names clear and business-oriented
- Remove outdated documents instead of letting them pile up
- Separate draft files from approved source-of-truth files
- Use descriptive filenames so Agents and humans can find them faster
Drive is not the same as memory
Drive stores durable reference material. Chat Session memory stores ongoing conversational context. Both matter, but they solve different problems:
| Layer | Purpose |
|---|---|
| Drive | Long-lived source documents and structured knowledge |
| Session | Temporary context for the current conversation |