JEV SCOPE CHALLENGE · EXPLORATORY RECORD

One visible match.
When is caution wrong?

Missing another same-product order can make a product-name request ambiguous. An exact, visible order ID can still settle the target. Switch only the coverage premise and inspect the saved decisions.

12 parent scenarios · 72 constructed inputs · new human review pending. Program-derived references, synthetic coverage premises, one wording family. These are recorded responses, not live calls. A template-aware program solves all 72.

Full report & budgets · 512-token control and execution repair · Frozen protocol · Milestone audit · Series home

The whole fixed grid

Decision configurationMap 0 /72Map 1 /72Strict complete parents /12

Jev's errors are unnecessary deferrals on explicit-ID requests with relevant omissions. Qwen's no-thinking readout predominantly accepts the destination. These interfaces do not establish either model's reasoning ceiling.

Provisional reference:

Exact visible state
Jev request and original returned JSON
Qwen record and generated trace, when available

All six inputs for this parent

InputReferenceJevQwen selected readout
Changing answers earns no credit unless both members are correct. Mapping changes are repeated measurements.

All six smoke cases

Exact smoke request and both recorded responses