Add ranking score pipeline doc - #78
Open
nS-101 wants to merge 1 commit into
Open
Conversation
Documents the four post-Phoenix scoring stages (base weighted score, author cold-start, author diversity decay, out-of-network discount) with formulas, default param values, and worked examples, plus a note on why slate_context intentionally stays stale for cached requests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/RANKING_SCORE_PIPELINE.md, a reference doc walking through the four scoring stages a candidate goes through after Phoenix predicts its action probabilities: base weighted score, author cold-start, author diversity decay, and the out-of-network discount.ranking_scorer.rs/author_cold_start.rsline numbers.slate_context/kon cached (paginated) requests: scoring always recomputes fresh for correctness, but theslate_contextfield written back onto the output candidate intentionally keeps the originally-cached value (verified against the existingrecomputes_contexts_for_scoring_on_cached_poststest) for a stable signal downstream tovm-ranker.This is documentation only — no code changes.
Test plan