- Sources read: 5
- Canon files updated: 2
- Radar entries: 2
Other changes reviewed today:
- Added a path, off by default, that sends VMRanker safety labels marking posts that solicit replies, shares or clicks.
- Taobao released MARS, in which a small LLM picks the recommendation pipeline configuration for each user, together with A/B results on five surfaces.
- The two Meta Engineering posts from 11-18 are about ads ranking development tools, so they were not added to the canon.
1Teacher score storage changed to serving scores and is on — X
Source xai-org/x-algorithm@b551517 — xAI, 2026-11-19, code. In these notes' numbering, this is Gen4+Gen67.4+N is the number these notes assigned in order to commits after the 2026-08-13 Gen4 release).
Background In X For You, Phoenix (a Grok-based Transformer ranker) outputs per-action probabilities such as like, reply and report for each candidate post, and a weighted sum of these sets the order. The previous day's commit added a teacher re-scoring path, off by default, to home-mixer (the service that assembles For You requests). In distillation (a method that uses a larger model's predictions as another model's training target), the teacher is the model that supplies the answers. This commit reworked that path to store serving scores without a separate model call and turned it on by default.
What we learnedA. The probabilities from the production ranker become the teacher label as they are
The teacher label is now the probability Phoenix already produced at serving time, copied over, rather than a fresh query to a separate cluster verified —
teacher_score_side_effect.rs:48-79- The new function
served_probpicks the candidate'sphoenix_scoresfield for each action name (for examplefavorite_score,reply_score,report_score) and returns it. - The test is named
served_probs_are_the_scores_the_ranker_returned. - The teacher cluster name, the sampling rate, the top-64 limit and the 2-second timeout parameters were deleted.
- The new function
Only posts actually shown are stored, and the same source post is kept only once verified — same file
teacher_entry- The previous day's version re-scored up to 64 candidates, including the top of the weighted sum among those that were dropped.
- The previous day's version also wrote per-candidate inputs to the cache, but this version writes only one bundle of per-head probabilities.
This path is on by default, and the 21 heads to store are filled in by default verified —
params/param.rs:1269-1286- The TTL is 3000 seconds (50 minutes), the same as before.
param!(EnableTeacherScoreSideEffect, bool, "rust_home_mixer_enable_teacher_score_side_effect", true); param!(TeacherActionIndices, Vec<u64>, "rust_home_mixer_teacher_action_indices", vec![1, 4, 5, 6, 11, 12, 13, 14, 16, 17, 21, 23, 25, 29, 30, 32, 33, 37, 38, 39, 59]);It runs for every request whose resolved Phoenix cluster is a production cluster, with no sampling verified —
teacher_score_side_effect.rs:132-141- The conditions are
is_prod(), a request that is not a cache reuse, the training-request cache switch on (on by default), andis_prod_cluster(resolve_cluster). - The production clusters are
Experiment1FouandExperiment2Fou, and the verdict function was moved tophoenix_scorer.rsand shared.
- The conditions are
What we learnedB. A role now exists for sending engagement-soliciting labels to VMRanker
- A path, off by default, now exists in which home-mixer looks up safety labels marking posts that solicit replies, shares or clicks, marks the matching candidates, and sends them to VMRanker (the ranker service that handles DPP slate re-ranking and the weighted sum) verified —
vm_ranker_engagement_labels.rs- There are three labels,
PROMOTES_REPLIES,PROMOTES_SHARESandPROMOTES_CLICKS, carried in the experiment payload asreply_ineligible,share_ineligibleandclick_ineligiblerespectively. - The switch is
VMRankerSendEngagementIneligible(default false), and only the top 200 candidates by weighted sum are looked up (param.rs:663-674). - The lookup timeout is 80ms, and if it fails no marks are set.
- There are three labels,
- What VMRanker does with this mark is not public verified — the same commit has no changes in the vm-ranker directory.
- Because the field name is ineligible, we infer it is used to remove the probability of the matching action head from the weighted sum inferred. The only evidence is the field name and the label names.
What we learnedOther changes
- A mode that spreads the remaining ad slots evenly across the page when ad slots are trimmed was added, off by default verified —
ads/slot_spread_blender.rs- The switch is
AdsUserLoadEvenSpread(default false), and the number of slots to keep is decided by rounding up the fractional part of the expected value using a request id hash.
- The switch is
- For mention notifications on the notification surface, a rule was added that drops posts containing keywords the viewer muted for notifications verified —
visibility-filtering/rules/tweet_rules.rs- Keywords with the "exclude accounts you follow" option apply only when the viewer does not follow the author.
- A loader was added to the Phoenix training data that reads the user's long-term author profile features (per-author engagement count, strong engagement count, time since last engagement, average dwell time) verified —
long_term_author_profile.py - A field for the advertiser's first run time was added to the ads proto, and the action control code in abuse-enforcement-service was cleaned up verified — commit diff
Canon update services/x.md The reference commit in ## Summary was raised to b551517. The introductory sentence of ### Training and serving infrastructure and the teacher paragraph were rewritten as "serving score storage, on by default", and the earlier form was moved into a change log bullet of that section. The teacher re-scoring definition in the ## Glossary table was corrected. An engagement-soliciting label sending bullet was added under the Phoenix section's debias bullet, and an even-spread bullet was added to ## Ads. One row each was added to the ## Sources reference sha table and the change log summary table.
Why it matters ⚠ Claim changed: the teacher path changed from "off by default, re-scoring with a separate larger model" to "on by default, storing production ranker scores". The teacher is therefore not a larger model but the Phoenix currently serving. We infer that the student trained on these labels is a retrieval or lightweight ranker, but no consuming code exists, so we leave it as an inference.
Corrections
- Yesterday's x.md presumed the teacher path to be "distillation data that uses a large model's predictions as the training target of a small serving model". Because the teacher became the production serving model itself within a day, the presumption was corrected to "data that uses the production ranker's predictions as another model's training target".
topics/andradar.mdhad no sentence about the X teacher.
Radar
- Taobao MARS — an LLM sets the recommendation pipeline configuration for each user — arXiv 2611.24006. A Qwen3-0.6B agent picks per-user retrieval quotas and fusion weights in near-line, and it reports GMV of up to +7.34% in a 2-week A/B on five Taobao surfaces.
- ARGUS ads CTR — reuse offline history tokens for each candidate — arXiv 2611.24283. It distills a compressed-history ranker from a teacher that sees the uncompressed history, and it reports conversion value of +4.65% in an ads A/B.
What to check next
- The training-side code that reads the X teacher labels — once it shows which model is the student, the inferred can be resolved.
- Where VMRanker uses the engagement-soliciting mark — if vm-ranker changes are released, check whether it removes the matching head from the weighted sum. For now it is inferred.
- Two r/RedditEng candidate new posts — WebSearch found only the titles, and we could not confirm the reddit.com original URL or the body. They are "Introducing a Global Retrieval Ranking Model in the Ads Funnel" (about 11-19) and "An In-Depth Look at the Notifications Recommender System" (about 11-16).
- The two Meta Engineering posts from 11-18 are about ads ranking development tools, so they were not added to the canon — spreading ads ranking techniques with AI agents, Standard Model Templates. They did not mention the organic feed.
- The other sources checked today had no new feed-related material. The latest Netflix blog post was the 11-17 AI Discover post seen yesterday, and the SEC had no 10-K, 10-Q or earnings 8-K filings. Of the 30 arXiv cs.IR items, 8 were new submissions (2026-11-18), and two of them passed.
Lookup failed: r/RedditEng RSS — 2026-11-20 HTTP 404 (after the 2026-11-13 notice that RSS support was ending) Lookup failed: redditinc.com/news — the command to look up the listing page was denied in this session, so we could not confirm it Lookup failed: ai.meta.com/blog — we could not open the listing page directly, so we cross-checked only through WebSearch