Query Hydration
Fetch user context: engagement history, following list, preferences, starter packs, impression bloom filters
"We have eliminated every single hand-engineered feature and most heuristics from the system. The Grok-based transformer does all the heavy lifting."
Orchestration layer that assembles the For You feed using CandidatePipeline framework. Coordinates all stages from hydration to selection.
In-memory post store for in-network posts. Sub-millisecond lookups from accounts you follow. Consumes Kafka events, auto-trims old posts.
ML engine for out-of-network content. Two-tower retrieval + Grok-based transformer ranking with candidate isolation.
Content understanding pipeline with classifiers, embedders, and task execution for spam detection, categorization, PTOS policy.
Fetch user context: engagement history, following list, preferences, starter packs, impression bloom filters
Thunder (in-network, followed accounts) + Phoenix Retrieval (out-of-network, ML-discovered)
Enrich with post data, author info, media entities, video duration, subscription status
Remove duplicates, old posts, self-posts, blocked authors, muted keywords, seen content
Phoenix ML predictions + weighted combination + author diversity attenuation
Sort by final score, select top K candidates
VFFilter (deleted/spam/violence/gore) + conversation dedup
Phoenix predicts 15 engagement probabilities. The weighted scorer combines them into a final score:
Positive actions (like, repost, share) have positive weights. Negative actions (block, mute, report) have negative weights, pushing down undesirable content.
ML system retrieving, ranking, filtering content for personalized user feeds.
Grok-based neural network architecture for predicting engagement probabilities.
Neural retrieval with separate user and candidate towers for similarity search.
Attention masking ensuring candidates only attend to user context for cacheable scores.
Content from accounts the user follows, retrieved via Thunder.
ML-discovered content via Phoenix similarity search across global corpus.
Review README.md for overall architecture. Four main components: Home Mixer (orchestration), Thunder (in-network), Phoenix (ML), Grox (content understanding). Read component READMEs for details.
Execute phoenix/run_pipeline.py as single entry point: retrieval -> ranking from exported checkpoints. Pre-trained mini Phoenix model (~3GB Git LFS) included for out-of-box inference.
Use candidate-pipeline framework to add new sources, hydrations, filters, scorers. Implements traits: Source, Hydrator, Filter, Scorer, Selector, SideEffect with parallel execution.
Add new scorers by implementing the Scorer trait. Receive candidates and user context, return scores for weighted combination and author diversity adjustment.
Use home-mixer/ads module for ad injection and positioning. Includes brand-safety tracking respecting sensitive content boundaries.
Interactive visualization of entities and relationships from the repository. Click nodes to open in URIBurner resolver.
Explore Knowledge Graph using SPARQL
Graph: DAV/demos/daas/x-algorithm-minimax_m2.5free-1.ttl