R0041/2026-03-28/Q001/H3¶
Statement¶
Vendors are addressing sycophancy through general model alignment and training improvements rather than as a configurable enterprise product feature. Sycophancy reduction is embedded in model behavior at training time, not exposed as an enterprise configuration option or distinct product tier.
Status¶
Current: Supported
The evidence consistently shows that all major vendors addressing sycophancy do so through model-level interventions: post-training reward adjustments (OpenAI), constitutional AI principles (Anthropic), and general alignment research. No vendor offers an enterprise API parameter, configuration toggle, or product tier specifically for sycophancy control. The closest approach is Anthropic's system prompt guidance ("Don't be a sycophant!") and their soul document's emphasis on honesty over agreeableness, but these are model-level behaviors, not enterprise-configurable features.
Supporting Evidence¶
| Evidence | Summary |
|---|---|
| SRC01-E01 | Sycophancy reduction achieved through reinforcement learning training, not enterprise configuration |
| SRC02-E01 | OpenAI addresses sycophancy through model training adjustments, specifically reward signal tuning |
| SRC05-E01 | OpenAI Model Spec embeds anti-sycophancy as a model behavior principle |
| SRC06-E01 | Anthropic's soul document frames anti-sycophancy as a core character trait, not a configurable feature |
Contradicting Evidence¶
| Evidence | Summary |
|---|---|
| SRC04-E01 | Anthropic's Petri tool represents dedicated sycophancy evaluation infrastructure, suggesting movement toward treating it as a distinct, measurable property — which could evolve into an enterprise feature |
Reasoning¶
The evidence strongly supports H3. Every vendor that addresses sycophancy does so at the model training level. OpenAI adjusted reward signals in post-training for GPT-5. Anthropic uses constitutional AI principles and dedicated evaluation but does not expose sycophancy controls to enterprise customers. Microsoft/Azure offers content safety filters but none address sycophancy specifically. Google's approach appears to rely on general alignment. The pattern is clear: sycophancy reduction is treated as a model quality property, like reducing hallucination, rather than a configurable enterprise feature.
Relationship to Other Hypotheses¶
H3 is the nuanced middle ground between H1 (dedicated enterprise features) and H2 (no vendor attention). It is the best-supported hypothesis. The distinction from H1 is subtle but important: vendors are investing heavily, but the investment produces better models for everyone rather than enterprise-specific sycophancy controls.