Knowledge base
Use retrieval when answers must come from trusted source material.
The knowledge base is where Reticuli turns source material into searchable context for the assistant.
In plain English: the assistant looks up relevant passages before answering.
Source files become searchable knowledge after indexing. Folders organize the canvas but do not become knowledge by themselves.
Use knowledge when
- facts change over time
- answers must cite or follow source material
- users ask about policies, product details, or procedures
- you want to update knowledge without retraining behavior
What makes a good source
A good source is current, specific, and trusted.
Strong sources:
- one policy per file
- clean help center articles
- current product documentation
- focused SOPs and playbooks
- short notes with clear instructions
Weak sources:
- old exports nobody trusts
- long mixed documents with unrelated topics
- duplicate versions of the same policy
- screenshots without text
- private content the assistant should never reveal
Embedding model rule
Reticuli uses an embedding model to convert documents into searchable vectors.
Use the same embedding model for indexing and querying. If the index and query use different embedding models, retrieval quality can become random and unusable.
Syncing knowledge
After changing sources or retrieval settings, sync the knowledge base. Then retest the same prompts in the playground.
Source workflow
- Add files, URLs, notes, or folders on Data.
- Wait for source status to become ready.
- Remove failed, duplicate, or stale sources.
- Sync or re-index when source set changes.
- Ask the same Playground prompts again.
- If answer still misses obvious content, split or clean the source.
Practical tests
Ask:
- What source did the assistant use?
- Did it answer from the newest policy?
- Did it miss an obvious document?
- Did it quote a fact that is not in the source set?
Source decisions
| Symptom | Fix |
|---|---|
| Correct doc ignored | Split large file or add clearer title/section text |
| Old policy used | Remove old source and re-index |
| Answer mixes unrelated topics | Split project or separate source folder |
| Screenshot content missing | Add text source or image understanding output |
| Good facts but poor tone | Add training examples, not more docs |