Documents change
When PDFs, manuals, or policies update, old chunks can keep answering inside your assistant.
Track document versions, inspect chunk diffs, audit stale knowledge, and understand exactly what changed before your AI assistant answers.
12 {
13 "chunk_id": "usr_9921",
14 - "content": "Checkout is at 10:00 AM."
14 + "content": "Checkout is now 11:00 AM for verified guests."
15 "embedding_model": "BAAI/bge-small-en-v1.5",
16 }
When PDFs, manuals, or policies update, old chunks can keep answering inside your assistant.
RagTrack keeps old versions for audit, but searches latest versions by default.
Track which model, source file, and version produced the knowledge your RAG app uses.
Debugging a bad answer is easier when you can inspect exactly what changed.
Snapshot source documents into document versions with hashes.
$ ragtrack status
Documents: 12
Versions: 37
Chunks: 1,284
Compare latest knowledge against the previous version.
+ Added: 3 chunks
- Removed: 1 chunk
~ Modified: 5 chunks
Start with keyword search, then add FastEmbed for semantic search.
$ ragtrack search "wifi password"
Result #1
house_rules.pdf / v3
Add Markdown, TXT, PDF, and DOCX files from your project or web UI.
RagTrack hashes files, detects changes, and creates a new version only when needed.
Use status and diff commands to understand what changed before shipping.
Query latest chunks from your assistant, scripts, or local web interface.
$ ragtrack ingest ./docs
> Processing supported documents. Generated versioned chunks.
$ ragtrack search "wifi password"
> Returning latest chunks with source document and version.