Skip to main content

​
What is the IP Vault?

The IP Vault is your personal file storage. When you upload documents here, your digital twin can read and reference them when answering your questions. Simple workflow:
  1. Upload your files (PDFs, documents, spreadsheets, etc.)
  2. Ask questions about your content
  3. Get answers that reference your uploaded materials
This is useful for uploading course materials, research papers, company policies, product documentation, or any content you want your digital twin to know about.
By default, personal files that go 90 days without being used move to the Trash (each use restarts the count), and a Digital Twin’s files are kept forever. See How long files are kept.
File Security: All files in the IP Vault are protected by a three-tier access control system — Public, Private (default), and Confidential. See File Access Control for details.Sign-in required page displayed when accessing a private file

​
When Does My Digital Twin Use My Files?

Your digital twin automatically searches your uploaded files when you:
  • Ask questions related to content you’ve uploaded
  • Select specific files to include in a conversation
  • Reference topics covered in your documents

​
Two retrieval modes — RAG and KAG

Two complementary pipelines can process every file after upload: RAG always runs; you don’t have to choose between them. When KAG is enabled — by your Digital Twin’s administrator for its shared vault, or by you for your personal files with Enable KAG Fusion for my files in Your Profile › Knowledge — your Digital Twin searches both the passages and the map, so answers draw on the direct text and the connections between things — unless you choose RAG in Knowledge. You can also browse the resulting graph in the Tree of Knowledge view.
KAG processing happens after each passage has been cleaned up, alongside the indexing step. You can see live progress in each file’s preview under Knowledge Graph — KAG, including how many segments KAG has extracted entities from and any errors that came back from the extraction model.

​
KAG Support: meaning-aware retrieval

Plain RAG is excellent at finding the right passage, but some questions need the right connections — how people, policies, and concepts relate across many documents. That’s what KAG (Knowledge-Augmented Generation) adds. When KAG Fusion is enabled for a vault, Pria builds a knowledge graph — a “tree of knowledge” — from your documents, extracting the entities and the relationships between them, and then merges what it finds in the graph with what the ordinary file search finds, so a single answer draws on both. KAG is always an extra layer on top of the normal file search, never a replacement — the ordinary search always runs.
Infographic titled “KAG augments RAG and outperforms GraphRAG.” Four stages: content sources (documents, course files, policies, videos, data tables); RAG finds relevant passages by similarity; KAG extracts meaning — people, topics, dates, and how ideas connect — into a living knowledge map; and better conversations with fewer tokens, more accurate answers, and traceable evidence. A comparison at the bottom shows GraphRAG as graph-search-only versus KAG as retrieval plus meaning plus reasoning context plus audit trail.

How Pria's KAG augments RAG — and why it's the stronger enterprise pattern compared to GraphRAG.

​
How a grounded answer comes together

  1. Content sources — documents, course files, policies, videos, and data tables become searchable once indexed.
  2. RAG finds relevant passages — matching by meaning surfaces the specific text that answers your question (precise lookup).
  3. KAG extracts meaning — entities (people, topics, dates) and the relationships between them form a living knowledge map, connecting ideas that no single passage spells out.
  4. Better conversations — answers combine the direct text with that structured context, and every claim traces back to a source file you can open.
A popular alternative pattern, GraphRAG, answers from a knowledge graph alone. Searching only the graph tends to miss passages that were never distilled into an entity, leans on higher token usage to walk the graph, and is harder to trace back to an original source. Pria’s KAG keeps the dense RAG leg and adds the graph plus an audit trail of evidence, so you get the best of both:The payoff shows up most on complex questions that thread through several documents (“how does this policy affect that team’s approvals?”) rather than sitting in one paragraph.
Because KAG builds a graph from every file, it runs an extra processing pass on top of the normal indexing — so it uses more credits than plain RAG, both when first enabled (existing files are processed again) and as new files are added. Enable it where the richer answers are worth the processing. You can watch extraction progress in each file’s preview under Knowledge Graph — KAG, and browse the finished graph in the Tree of Knowledge view.

​
Relevance Scores

When your digital twin finds matching content in your files, it shows a relevance score indicating how close in meaning the match is to your question. Matches are found by meaning, not just keywords, and scored on a 0–100% scale — the closer a passage is to what you asked, the higher its score. By default, results below 45% relevance are filtered out. Administrators can adjust this minimum relevance threshold to trade breadth (more results) against precision (only the closest ones).
For administrators: You can configure the minimum relevance threshold in Instance Settings › Knowledge (Document Search Affinity (%)). You can also disable file uploads for users while retaining upload capabilities yourself, to control what content enters the knowledge base.
Your digital twin uses a technology called RAG (Retrieval Augmented Generation) to search your files. Here’s what happens behind the scenes:
1

File Processing

When you upload a file, the system breaks it into smaller sections (segments) and turns each section into a numeric fingerprint of what it means, called a vector embedding — a long list of numbers chosen so that two passages about the same thing get similar numbers. Embeddings are generated by a dedicated AI model (e.g., OpenAI text-embedding-3-small, Amazon titan-embed-text-v2, or Google gemini-embedding-001).RAG Example
2

Question Analysis

Your question is converted into a vector embedding using the same model, so the system can compare your question against every section of your files by meaning.
3

Finding Matches

Pria compares the meaning of your question against every indexed section of your files and ranks the closest matches by relevance score.k-NN Example
4

Relevance Threshold

Results below a minimum relevance threshold are filtered out (default: 45%). Administrators can adjust how strict the matching is:
  • Higher threshold: Only highly relevant content is included — better precision
  • Lower threshold: More content is included — better recall, but may be less directly relevant

​
Segment Size and Search Accuracy

When a file is processed, it is split into segments (also called “chunks”) before being converted into vector embeddings. The size of these segments has a direct impact on how accurately your digital twin retrieves relevant content.Research findings from studies by Chroma Research and multi-dataset analyses consistently show an inverse relationship between segment size and retrieval precision:Key insights from the research:
  • Smaller segments match queries more precisely because the vector embedding represents a focused piece of content rather than a broad summary of many topics.
  • Larger segments preserve more surrounding context but introduce noise — the embedding averages over more content, diluting the signal for any single topic.
  • Industry defaults (e.g., 800 tokens with 400-token overlap) were found to score below average across all retrieval metrics.
  • The optimal size depends on query type: fact-based questions benefit from smaller segments (256-512 tokens), while analytical questions requiring broader context may benefit from larger ones (1024+ tokens).
At Praxis, a segment is 2,000 characters by default — roughly 500 tokens — and can never exceed 8,000 characters (about 2,000 tokens). The default keeps segments small enough for precise search; an administrator can pick a different size for a Digital Twin (from 1,000 to 6,000 characters). The 8,000-character cap accommodates the input limits of all supported embedding models — including OpenAI, Amazon Titan, and Google Gemini — so search stays precise without fragmenting content so aggressively that context is lost.
You can view and edit your file’s segments using the RAG Segments action in your file management options. Each segment shows its character count and the embedding model used to index it.