Skip to content

Glossary

Key terms used throughout hypar and in RAG systems generally.

TermMeaning
ChunkA bounded piece of a document (~400 tokens). The unit of retrieval. See RAG Pipeline.
EmbeddingA fixed-length vector (768 dimensions in hypar) that represents a chunk's semantic meaning. Produced by an embedding model.
pgvectorPostgreSQL extension that stores vectors and computes cosine distance. hypar's default vector store.
BM25Classical keyword-relevance score; complements semantic search on names, codes, and literals that embeddings often miss.
Hybrid searchWeighted blend of vector similarity and BM25, controlled by the parameter alpha in [0, 1]. See Hybrid Search & HyDE.
HyDEHypothetical Document Embeddings: the LLM drafts a short hypothetical answer first, then embeds that text as the query vector. Often improves recall on factual Q&A.
MMRMaximal Marginal Relevance: re-ranks retrieved chunks to balance relevance vs. diversity, controlled by lambda.
top-KHow many chunks survive filtering and are shown to the LLM as context.
Tool callThe LLM decides to invoke a function (here searchKnowledgeBase) instead of replying directly. Powered by the Vercel AI SDK.
Agent / search modeauto = LLM decides whether to search; search = always retrieve from KB; direct = skip retrieval entirely. Configurable in Settings.
HNSWHierarchical Navigable Small World: the index type used on the embedding column for fast approximate nearest-neighbour search.
Cosine similaritySimilarity metric between two vectors. 1.0 = identical direction, 0.0 = orthogonal. hypar uses a score floor of 0.2.
IngestionThe process of parsing a document into chunks, embedding each chunk, and storing them in the database. Runs as a durable background workflow.
WorkspaceAn isolated scope for documents and settings, shared among members with different roles. See Workspaces.