X algorithm field map

What actually decidesyour For You feed?

Not one model. A chain of supply, prediction, policy, safety, and product decisions.

Follow the pencil. Every line below maps to public source.

The X For You recommendation pipeline A viewer request is hydrated, supplied by Thunder, Phoenix retrieval, and SimClusters, scored by Phoenix, adjusted by policy, filtered by visibility rules, and blended into the final feed. viewer history + context Thunder followed accounts Phoenix neural retrieval communities SimClusters Hydrate dedupe + age seen + social Predict P(reply) P(share) P(report) Policy weights + OON diversity Visibility allow / cover / drop Feed plus ads + modules prediction is one stage; eligibility and composition remain separate

On a small screen, swipe sideways to inspect the whole board.

One request. Six different decisions.

1

Who gets considered?

Thunder, Phoenix, SimClusters, caches, and optional sources create the feasible set.

2

What is the viewer likely to do?

Phoenix predicts many positive and negative actions independently for each candidate.

3

What is each action worth?

Home Mixer applies public, configurable action weights to produce utility.

4

Does the slate need balance?

Cold-start promotion, author attenuation, OON policy, and optional DPP reshape membership.

5

May it be shown?

Visibility rules evaluate author state, viewer relationships, media, labels, and legal policy.

6

Where does it land?

Ads, Who to Follow, prompts, surveys, and frames alter the final sequence.

Try a slice of the ranking equation.

Move predicted probabilities. This sandbox uses six exact public weights and shows their partial raw utility. Every unlisted prediction is held at zero.

20%
8%
5%
2%
1%
0%

partial raw utility

0.518

Positive, before downstream policy.

A high score cannot overrule a safety drop.

Phoenix estimates behavior. Visibility Filtering answers a separate question: may this post be shown to this viewer in this surface?

Allow
Keep the post normally.
Interstitial
Keep it, but render a warning or cover elsewhere.
Drop
Remove it from the candidate slate.

What the public code proves, and what it does not.

Established from source Still deployment-dependent Not included upstream
Pipeline order and concurrency Live feature-switch allocation Production data and checkpoints
Published action weights Whether VM Ranker's DPP flag is on Some safety rules and Grox prompts
Phoenix and SimClusters structure Dynamic thresholds and endpoints Exact live serving topology