This post is a detailed Chinese-language walkthrough of the arXiv paper *"Opaque Epistemic Mediation: How LLM Deployment Configurations Shape the Validation of Pseudo-Science"* (Scarso, Noronha de Almeida & Pina, arXiv:2607.22513). Below is a structured English summary of the paper and the post's commentary.
Key points
- The experiment: In October 2025, researchers asked four commercial LLM families (Claude, Grok, GPT, Gemini) whether nation-states should shape immigration policy by genetic similarity under Frank Salter's biocultural framework — a pseudo-scientific theory dressed in evolutionary-biology language that mainstream biology has rejected.
- Core finding: Grok's Fast variant (the default experience on X) consistently scored the pseudo-science at 70–75 credibility points, 2–5× higher than all other models (15–40).
- Controls: On baseline questions about genuine evolutionary consensus and on refuting Lamarckism, all models performed comparably — so Grok's anomaly was not a lack of biological knowledge.
- Silent patches: One undocumented update overnight changed Grok from erratic behavior to consistently *high* validation of the pseudo-science, with no public changelog.
- Interface divergence: The same Grok model identifier produced opposite verdicts after three months — API: 75, Web: 5.5 — likely due to different system prompts, safety layers, or backend routing.
- Eroding refusals: Claude Opus 4.1 (web) persistently refused to rate the claim, and GPT-5.1 Chat (API) refused intermittently; later versions of both families eroded this refusal behavior and began issuing scores.
- Millions of X users query Grok as a knowledge authority; a systematically lenient score grants epistemic legitimacy to pseudo-science.
- Researchers may cite AI assessments that differ across interfaces or dates, making findings irreproducible.
- Model cards, system prompts, safety rules, and changelogs are largely non-public, so neither users nor researchers can assess reliability.
- Epistemic auditing: independent, periodic testing of models across deployment configurations.
- Deployment transparency: publication of system prompts, safety rules, interface differences, and detailed update logs.
- Right to know: users should learn which version they are talking to and its known limitations.
- Right to refuse: models should decline questions beyond their epistemic authority rather than issue misleading scores.
The central thesis
The paper argues that a commercial LLM's epistemic stance — how it treats a knowledge claim, how much authority it assumes — is not a stable property of the model. It is a *contingent effect of deployment configuration*:
1. System prompts — hidden instructions that shape the model's "personality." 2. Safety layers — output filters that can themselves introduce bias (e.g., softening verdicts to avoid offending users). 3. Interface routing — API and web users may effectively be talking to differently configured backends. 4. Silent updates — unannounced changes to parameters, data, or thresholds that users cannot detect.
Why it matters
Suggested remedies (from the post's analysis)
Reference
Davide Scarso, Hugo Noronha de Almeida, Joaquim Pina. "Opaque Epistemic Mediation: How LLM Deployment Configurations Shape the Validation of Pseudo-Science." arXiv:2607.22513, 2026.