Fetching from the wire…
Public story · 2026-07-23 · high
An 8B version beat a 70B reward model and a 235B rubric generator at supervising the policy, per the paper.
Why now: DynamicRubric appears in a paper posted to arXiv on July 23, 2026, which says it already runs across WeChat Search's production traffic.
WeChat Search replaced its static reward model with an evaluator that rewrites its own grading rubric for every batch of responses, per a paper posted to arXiv (2607.20083). The new system, called DynamicRubric, now grades every response across WeChat Search's full production traffic, tens of millions of requests a day.
The problem is specific. As a policy model improves during reinforcement learning, its sampled responses start looking alike. A fixed evaluator's score gaps between them shrink toward zero, and with no gap there's no training signal.
The paper traces this to a probability-allocation argument. The gain from shifting probability mass between two candidate responses equals the evaluator's score gap between them. Collapse the gap and you collapse the gradient.
DynamicRubric's fix is to generate weighted binary rubric items conditioned on the candidate set being graded. That replaces a rubric written once and reused. No new loss function, no bigger model.
The size result is the part worth sitting with. An 8B DynamicRubric evaluator outperformed a 70B reward model and a 235B static rubric generator at supervising policy training, per the paper. That inverts the usual assumption that judge quality tracks judge size. Here it tracked whether the judge's rubric moved with the policy.
The paper doesn't say how often the rubric regenerates in production, or what the compute overhead looks like at that request volume. For teams running LLM-as-judge on a fixed prompt, that's a case for tying the judge's refresh cycle to the policy, not manual updates.
Each link below shares sources, entities, or timing with this story.
Satya Nadella said companies routing everything through a single proprietary lab may not survive. His argument: you hand that lab your most sensitive business context, and the lab can turn it against you as a competitor. His prescription is an orchestration layer — keep the ha...
Simon Willison highlighted Sophie Alpert's short internal policy on AI-assisted writing, whose load-bearing rule is accountability: "You must stand behind every idea and every sentence in your docs," because you can't excuse a bad passage by blaming the LLM, and doing so waste...
Allen Bargi's August 15 post hit 302 points arguing that AI collaboration rewards context-sharing, examples, and feedback over precise instruction (Hacker News). The pushback holds that the piece conflates management with leadership. mikeocool calls it "the most low effort ver...
Willison launched datasette-apps (0.1a2) on June 18, hosting self-contained HTML+JS apps in a sandboxed iframe that run SQL against your data, read-only by default. He frames it as "Claude Artifacts reimagined for Datasette," artifacts backed by a JSON API to a relational data...
His conclusion is DuckDB matches or beats SQLite's safety for untrusted queries, but only with enable_external_access=false, lock_configuration=true, and a watchdog thread, since DuckDB lacks SQLite's opcode-based query timeouts. He ships a safe_duckdb.py helper and a Datasett...
CCP announced the migration covering code that has run on Stackless 2.7 since 2010. The approach is to run futurize across the codebase and then manually review roughly 20,000 places where Python 2 and 3 behavior diverges, including integer division (Simon Willison). No comple...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.