0x00 한

Research / Daily reports

  • Sources read: 1
  • Canon files updated: 2
  • Radar entries: 1
In one lineX's VMRanker received code that removes the prediction for an action from the score on posts labeled as inducing replies, shares or clicks. The switch is off by default.

1Scores for the targeted action can now be removed from engagement-bait posts — X

Source xai-org/x-algorithm@269340c — xAI, 2026-11-21, code. In these notes' numbering, this is Gen4+69 (Gen4+N is the number these notes assigned, in order, to commits after the 2026-08-13 Gen4 release).

Background The final score of X For You is the sum of per-action probabilities predicted by Phoenix (a Grok-based Transformer ranker), each multiplied by a weight, and VMRanker (the service that handles the weighted sum and DPP slate reordering) computes this weighted sum. Engagement-bait posts such as "Please reply" or "Share and get ○○" get high reply and share probabilities and benefit in the weighted sum. The 2026-11-19 commit (Gen4+67) only built the path that flags candidates carrying such safety labels and sends them to VMRanker; how VMRanker uses the flag was left empty. This commit fills in the VMRanker handling and adds a popular-video retrieval index and a teacher-score distillation loss.

What we learnedA. When an engagement-bait label is present, only that action's prediction is dropped from the weighted sum

  • When a candidate carries a reply, share or click bait flag, VMRanker clears the Phoenix prediction for that action and then computes the weighted sum verified — vm-ranker/scoring/value_model.rs:214-237

    • home-mixer carries the flags in the experiment payload (extra information attached to each candidate) as reply_ineligible, share_ineligible and click_ineligible.
    • The share flag clears three heads together: share, DM share and copy-link share. Other heads such as like remain.
    if payload.reply_ineligible { scores.reply_score = None; }
    if payload.share_ineligible {
        scores.share_score = None;
        scores.share_via_dm_score = None;
        scores.share_via_copy_link_score = None;
    }
    if payload.click_ineligible { scores.click_score = None; }
    
  • The switch that turns on this handling is off by default verified — vm-ranker/params.rs:327-332

    • The switch is ExcludeIneligibleEngagementHeads (rust_home_mixer_vm_ranker_exclude_ineligible_engagement_heads).
    • The switch with which home-mixer sends the label (VMRankerSendEngagementIneligible, Gen4+67) is also off by default, so both switches must be on for scores to change.
    • The number of candidates removed per head is recorded in the vm_ranker_ineligible_head_candidates_total metric.
  • A test confirms that when a reply flag is present the score drops by exactly "reply weight × reply probability", and that it stays unchanged when the switch is off verified — vm-ranker/scoring/mod.rs:482-553

What we learnedB. An index was added that collects only videos that passed 10,000 views and 100 likes within 48 hours

  • A pipeline that builds a popular-video SID index (a retrieval index that groups posts by semantic ID) was added to the index service for Phoenix retrieval verified — phoenix-rankall/src/config/mod.rs:110-128, 262
    • The condition is a video post with at least 10,000 views and at least 100 likes. The time window is 48 hours.
    • Posts in the NSFW video index of the last 7 days are excluded, and only posts in the 2-day video index are kept. Both lists are read as post IDs from parquet files.
    • The processor is a new file, processor/sid_popular_video_processor.rs (167 lines), and a test confirms that a post is dropped if it misses either of the two thresholds.
  • This index was registered in the training and lookup-side proto as retrieval dataset 30 (POPULAR_VIDEO_2DAY) verified — recsys.proto
  • home-mixer can now attach a per-dataset top-k to the Phoenix retrieval request, but the default is an empty string, so the default request is unchanged verified — params/param.rs:22-27
    • The format is a string of "datasetName=k" pairs joined by commas (sources/phoenix_source.rs:168-175).
    • This commit has no default setting that makes requests actually look up the popular-video index.
  • Candidates from the two AI-generated video 2-day indexes (author label, model detection) are marked with a separate served type (a label for the path by which the candidate entered) verified — sources/phoenix_source.rs:177-186
    • The label is ForYouPhoenixRetrievalAiVideo, and the numbers of selected and unselected candidates are recorded in the PhoenixRetrievalAiVideoTweets stats.

What we learnedC. Teacher scores were kept for use as a distillation loss for the ranking model

  • The training code can now read the teacher score column of the training data and add a distillation (an approach in which one model uses the predicted probabilities of a larger model as its training target) loss to ranking model training verified — phoenix/xrex/models/recsys_overarch_model.py:57-69
    • There are two loss types, probability BCE and logit MSE, and the default is BCE (recsys_distillation_loss.py).
    • The default distillation targets are three actions: link open, ads MMP click and VQV (an action of actually watching a video for at least a set time) (teacher_distill.py:13).
    • An option (distill_bad_spans_ms) discards the teacher scores of rows shown within specified time ranges. We infer it is meant to exclude periods when the teacher misbehaved inferred. The only basis is that the name says bad spans.
  • This distillation is off by default verified — the default of the teacher name (distill_teacher) is an empty string, and no training config that sets it is in the same commit.
  • We infer that the serving scores home-mixer has logged since Gen4+67 are the source of this teacher score column inferred. The only basis is that both paths handle per-action probabilities under the name teacher, and the log conversion code linking the two is not in the repo.

What we learnedOther changes

  • A switch that restricts video carousel candidates to videos that arrived through MoE retrieval (a retrieval path that mixes several expert models) was added, off by default verified — params/param.rs:1538-1543
  • A switch was added, off by default, that keeps the Under the Hood (a transparency tool where users see the labels and feed scores of their own account and posts) trace card from being inserted for people who turned off the user setting verified — params/param.rs:817-822
  • The video length of a quoted post is now computed from the quoted content already received instead of a separate TES call (no policy change) verified — candidate_hydrators/quote_hydrator.rs
  • A live broadcast column was added to the training data, and an evaluation metric for broadcast posts was enabled in the immersive surface training config verified — configs/xrecsys.py
  • A constant was added so that the app conversion value label does not count events under $0.10 and uses an 8-hour label window verified — purchase_value.rs
  • Of the 59 changed files, 10 in the account enforcement service (abuse-enforcement-service) and 4 in grox are not directly related to feed ranking, so only the file list was checked verified — commit diff

"Candidates whose reply, share or click predictions were left out of the value model because home-mixer flagged that head as ineligible" — vm-ranker/metrics.rs metric description (code), 2026-11-21

Canon update services/x.md Raised the reference commit in ## Summary to 269340c. Rewrote the engagement-bait label bullet in the Phoenix section as "VMRanker can drop the corresponding head, off by default" and moved the home-mixer send path down to a sub-bullet. Added a popular-video index bullet to ### Phoenix retrieval index, added distillation loss sentences to the intro of ### Training and serving infrastructure and to the teacher paragraph, and changed the earlier inferred bullet to verified. Added one off-by-default switch sub-bullet each to the carousel item and the Under the Hood section, a distillation row to ## Glossary, and a 269340c row to the sources table and the commit summary table. Added one line of additional evidence on X's distillation loss to the ARGUS entry in radar.md.

Why it matters Two items left as inferred two days ago are now confirmed in code: the engagement-bait label is used to remove the score of the targeted action, and the teacher score is for distillation training. Both are off by default, so the For You ranking is currently unchanged. The engagement-bait handling does not cut the whole post; it removes only the share of the targeted action, so a labeled post keeps the score it earns from like and dwell predictions.

Corrections

  • The two r/RedditEng candidates in yesterday's daily ("Introducing a Global Retrieval Ranking Model in the Ads Funnel", "An In-Depth Look at the Notifications Recommender System") were not new posts. They are already listed in the sources of services/reddit.md as posts from 2024 and 2025, and the "a few days ago" marking added by a third-party mirror was stale.

Radar

  • Added one line of additional evidence on X's distillation loss to the ARGUS ads CTR thread.

What to check next