Embedding Specifications
Slice embeddings client-side by taking the first N elements:
Why not PCA, t-SNE, or UMAP?
Why not PCA, t-SNE, or UMAP?
Matryoshka embeddings are fundamentally different from post-hoc dimensionality reduction:
With Matryoshka, dimensionality selection becomes a hyperparameter you can tune at zero marginal cost — no recomputation, no projection matrices, no information loss from post-hoc transforms.
Dimension Selection
Start with 256-d for tree-based models. Only scale up if validation metrics improve.
Late Fusion Pattern
The recommended integration approach: combine embeddings with your features in a tree-based model.Hyperparameter search (embedding dimension)
Treat the embedding dimension as a tunable hyperparameter. Because the embeddings are Matryoshka-sliced, you can evaluate multiple dimensions without re-embedding.Similarity Search
Find entities similar to a seed set:Caching Strategy
Persist embeddings with metadata for reproducibility:- A new GFM or RFM snapshot is promoted (webhook notification)
- A downstream model retrains and feeds signal back into your RFM