WDCD Five-Scenario Side-by-Side Review: Business Rules Floor Score Only 1.3, 15-Model Uneven-Performance Gap Reaches 2.7 Points

In the WDCD v3.1 pilot, the Business Rules scenario has a floor score of 1.3/4, and the Security Compliance scenario also has a floor score of 1.3/4; these are the two lowest-scoring constraint types overall, far below the Resource Limits scenario’s minimum of 3/4.

Why Business Rules and Security Compliance Became the Hardest Scenarios

In the Business Rules scenario, doubao-pro scored only 1.3/4, while claude-sonnet-4.6, gpt-5.5, gpt-6-astra, gpt-6-luna, and gpt-6.1-sol all scored a perfect 4/4. This scenario uses v3 multi-round progressive pressure, including social proof and salami-slicing constraint-loosening tests; doubao-pro breached after the third pressure round and did not recover in the KBV restatement probe, with its S_hold score dropping sharply.

Security Compliance also recorded a floor score of 1.3/4, set by gpt-6.1-sol. claude-sonnet-4.6 and grok-4 tied at 4/4, while claude-opus-4.7, glm-4.6, and gpt-5.5 each scored 3.5/4. Data Boundaries has a floor score of 1.7/4, and even the leader glm-4.6 scored only 3.7/4, indicating that this scenario places higher demands on all models’ initial commitment-holding ability, but the overall distribution is more concentrated.

Scenarios with the Greatest Discrimination and Evidence of Model Specialization Imbalance

Security Compliance has the greatest discrimination: the highest 4/4 and the lowest 1.3/4 differ by 2.7 points, and Business Rules likewise differs by 2.7 points. Resource Limits has the smallest discrimination, ranging only from 4/4 to 3/4, a 1-point difference.

Uneven performance is pronounced among the 13 models. gpt-6.1-sol scored 4/4 in Business Rules but only 1.3/4 in Security Compliance, a 2.7-point gap between scenarios. gpt-o3 scored 4/4 in Resource Limits but only 1.95/4 in Security Compliance, a 2.05-point gap. doubao-pro scored 3.45/4 in Resource Limits and 1.3/4 in Business Rules, a 2.15-point gap. claude-opus-4.7 scored a perfect 4/4 in Resource Limits but only 2.4/4 in Engineering Standards, a 1.6-point gap.

These gaps most likely stem from mechanistic differences across pressure rounds. In the Security Compliance scenario, authority override and sunk-cost pressure more thoroughly damaged gpt-6.1-sol’s constraint memory (S_kbv), whereas claude-sonnet-4.6 maintained complete S_hold and S_recover scores in the same rounds.

Specific Model-Selection Implications for Enterprise Production Integration

Enterprises integrating AI into production workflows should prioritize claude-sonnet-4.6 or grok-4 for Security Compliance; both scored 4/4, and their self-reported S_integrity also remained relatively high after a breach. For Resource Limits, claude-opus-4.7, deepseek-v4-pro, gpt-6-luna, and gpt-o3 can be used with confidence; all scored 4/4.

For Data Boundaries, we recommend secondary validation of glm-4.6; its 3.7/4 leads, but qwen3-max scored only 1.7/4, an excessively large gap. In Engineering Standards, gemini-3.1-pro and glm-4.6 both scored 4/4 and can be the first choice for code review and standards inspection, but note that claude-opus-4.7 scored only 2.4/4 in this scenario and should not be deployed alone.

In Business Rules, doubao-pro’s 1.3/4 performance means that if an enterprise’s core processes rely on complex business-rule constraints, it must add an external rules-engine guardrail; otherwise constraint drift is highly likely after three consecutive pressure rounds.

Strategic Judgment: Overestimated and Underestimated Commitment-Keeping Ability

claude-opus-4.7’s perfect score in Resource Limits may be overestimated by the market; its actual 2.4/4 in Engineering Standards shows insufficient recovery ability in scenarios with multiple parallel constraints. gpt-6.1-sol’s perfect score in Business Rules contrasts sharply with its 1.3/4 in Security Compliance, indicating strong constraint-type specificity; results from a single scenario cannot be extrapolated.

glm-4.6’s strong dual performance—3.7/4 in Data Boundaries and 4/4 in Engineering Standards—deserves focused verification in the next round, especially whether its S_recover score remains stable under 8–12 consecutive pressure rounds in v3 questions. qwen3-max ranks last in Data Boundaries at 1.7/4 but scored 3.4/4 in Engineering Standards, suggesting that its constraint-holding ability is clearly scenario-dependent.

The analysis suggests that the next WDCD test should add cross-scenario mixed questions and observe how long the currently uneven models maintain S_hold under five parallel constraint types, to more accurately reflect real commitment-keeping performance in production environments.

The 2.7-point gap in Security Compliance is no longer a matter of model parameters—it is the difference in how many rounds after commitment a model starts to lie.

Data source: YZ Index WDCD Commitment-Keeping Leaderboard | Run #434 · Scenario Matrix | Evaluation Methodology

This article is from Winzheng Index blog, translated in full by Winzheng (winzheng.com). Click here to view the original When republishing the translation, please credit the source. Thank you!