docs(demo): nest evidence scorer in demo profiles - #686
Merged
Merged
Conversation
This was referenced Sep 8, 2026
behinddwalls
marked this pull request as ready for review
September 8, 2026 01:09
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 11, 2026 16:47
21834a0 to
624eb7d
Compare
behinddwalls
changed the title
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
2 times, most recently
from
September 11, 2026 21:10
8b60d14 to
9cd7195
Compare
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
2 times, most recently
from
September 14, 2026 19:38
3177410 to
52ce57b
Compare
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 14, 2026 19:48
52ce57b to
6865b99
Compare
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 14, 2026 19:50
6865b99 to
c1d904a
Compare
mnoah1
approved these changes
Sep 15, 2026
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 15, 2026 19:26
c1d904a to
0b6bcfb
Compare
behinddwalls
added a commit
that referenced
this pull request
Sep 15, 2026
## Summary ### Why? The RFC now has one public ranking interface. Keeping a Predictor package after that would leave a second factory the rest of the stack still had to delete. ### What? Widen `Scorer.Score` with the path-set snapshot. Move evidence under `scorer/evidence` as a Scorer wrapping a base. Heuristic, composite, and fake implement the same signature and ignore `paths` (composite forwards them). Delete the Predictor package and its mocks. The evidence factor for the land-stage batch is `Landing` / YAML `landing`. ## Test Plan - ✅ `make mocks && make gazelle` - ✅ `./tool/bazel test //submitqueue/extension/speculation/scorer/... //submitqueue/extension/speculation/generator/bestfirst:go_default_test //submitqueue/extension/speculation/speculator/standard:go_default_test` ## Stack - #682 (merged) - #683 ⬅️ - #684 - #686
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 15, 2026 19:43
0b6bcfb to
e2207ea
Compare
Write the outcome-predictor RFC example factors into every demo profiles.yaml so local runs show evidence revising ranking instead of silently staying at neutral 1.
Show type evidence wrapping a heuristic base with the RFC example factors, matching the ranking YAML the stack now wires.
Match the RFC and YAML key after BatchStateLanding.
behinddwalls
force-pushed
the
preetam/outcome-predictor-demo
branch
from
September 15, 2026 21:04
e2207ea to
2a3a7ee
Compare
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
2 participants
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
Why?
Demo profiles still showed a sibling
predictor:block, which the wired YAML no longer accepts.What?
Use
defaults.scorerwithtype: evidence, the RFC example factors (landingfor the land-stage batch), and a nested heuristicbasein fake/git/github profiles and the quickstart.Test Plan
Docs and YAML only; config parse is covered on the wiring PR.
Stack