Unverified50% confidenceFactExact time
The typical symptom of a slice that is too narrow is the agent repeatedly asking questions, requesting additional files, or making seemingly reasonable but actually wrong inferences based on incomplete information; the symptom of a slice that is too wide is the agent citing unrelated modules, carrying over old decisions, or diverging from the scope of changes during review.
1
Sources
50%
Confidence
Long-term
Relevance
10/25/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe symptom is that the throughput ceiling varies with request volume rather than model latency; if you are wrapping prompt retrieval in rate-limit retries, that is the sign.64% similarUnverifiedThe eval set should deliberately include uncomfortable cases such as ambiguous requests, out-of-scope requests, bad inputs, adversarial inputs, and high-risk cases, in order to expose real problems.64% similarUnverifiedTo change an agent's exception-swallowing behavior, a "failure visibility" metric needs to be added to the evaluation, for example requiring catch blocks to rethrow or return a distinguishable error type, otherwise the task is considered incomplete.61% similarUnverifiedIf the threshold is set too low, the review becomes a mere formality; if set too high, the Agent falls into a cycle of repeated fixing. 85 is only an example value, and real projects need to adjust it according to test maturity.61% similarUnverified过于敏感的异常检测会导致审批疲劳，使人工审核员对频繁告警逐渐失去警惕性60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1097619API
curl https://kongchang.com/api/v1/knowledge/claims/1097619MCP
get_claim(id=1097619)