Skip to main content

Embedding Specifications

Slice embeddings client-side by taking the first N elements:
Slice only prefix dimensions we explicitly support (16/32/64/128/256/512/1024). Avoid arbitrary cuts or mixing non-prefix subsets across experiments — that discards the Matryoshka structure and reduces information entropy.
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.
Find entities similar to a seed set:

Caching Strategy

Persist embeddings with metadata for reproducibility:
Refresh when:
  • A new GFM or RFM snapshot is promoted (webhook notification)
  • A downstream model retrains and feeds signal back into your RFM

Monitoring

Track embedding quality over time: