# Opaque Epistemic Mediation: How LLM Deployment Configurations Shape the Validation of Pseudo-Science

Source: [arXiv](https://arxiv.org/abs/2607.22513v1)  
Feed7 permalink: https://feed7.dev/p/2607-22513v1-0yf6na5  
Published: 2026-07-24T17:32:43.000Z  
Trust: Needs Review (needs_review)

## Why Included

The same model identifier produced sharply different judgments across API and web deployments. Treat model, interface, system configuration, and date as one versioned dependency.

## Source Summary

Researchers tested **four model families** from **October 2025 to February 2026** on a contested pseudo-scientific claim. Grok Fast scored it 70–75 versus 15–40 for the other families, while control prompts did not show the same gap.

## Practical Implication

For research agents, do not treat a model ID as a stable epistemic contract. Pin the deployment channel, record dates and configuration, and rerun domain-specific validation after silent service changes.

## Agent-Ready Context

Researchers tested **four model families** from **October 2025 to February 2026** on a contested pseudo-scientific claim. Grok Fast scored it 70–75 versus 15–40 for the other families, while control prompts did not show the same gap.

For research agents, do not treat a model ID as a stable epistemic contract. Pin the deployment channel, record dates and configuration, and rerun domain-specific validation after silent service changes.

The starkest mismatch was the same Grok identifier scoring **75 through the API and 5.5 on the web** three months later. This is a narrow case study, so it demonstrates deployment sensitivity rather than broad comparative model quality.

## Context Map

- Layer: benchmark
- Domains: research
- Topics: model-selection, agent-reliability, benchmark-integrity

## Uncertainty

- The starkest mismatch was the same Grok identifier scoring **75 through the API and 5.5 on the web** three months later. This is a narrow case study, so it demonstrates deployment sensitivity rather than broad comparative model quality.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.