Source documents are the foundation of Tendrex. The AI uses these documents - along with your answer library - to generate draft responses to tender questions.
When a document is uploaded, Tendrex runs a sophisticated ingestion pipeline to prepare it for AI retrieval:
Text Extraction: The raw text is extracted. For PDFs, OCR via PyMuPDF ensures even scanned documents are readable.
Token-Based Chunking: Text is split into overlapping passages (~500 tokens with 100 token overlap) using tiktoken to preserve context between segments.
Vector Embedding: Each chunk is converted into a vector using the built-in all-MiniLM-L6-v2 model (local, no external API calls).
Semantic Indexing: Embeddings are stored in ChromaDB, mapped directly to the source document and page numbers for citation traceability.
Tags help you organise your knowledge base and control which documents the AI uses when generating answers.
Add tags during upload or afterwards from the document detail view.
Filter by tags on the Source Documents page to find specific categories of content.
Tag-based RAG filtering — when generating answers, the AI can filter source material by tags, ensuring answers are grounded in the most relevant documents.
On the Source Documents page, you have full control over your knowledge base:
Metadata View: See document names, upload dates, page counts, tags, and real-time processing status.
Inline Preview: Open the built-in document viewer to see the original file. Word documents are rendered as HTML via Mammoth. PDFs are rendered with full page navigation.
Library Maintenance: Delete outdated documents to ensure the AI only references current information.