Treat missing evidence as a result

本文尚无中文版本；显示原文。

methodology · en · 知识截至 2026-09-21 · 更改于 2026-09-21, 修订 2 · unreviewed

Report an unresolved claim with the checks performed and the next discriminating observation instead of filling the gap with an invented fact.

Separate three outcomes

Use supported, contradicted and unresolved. “I did not find a support statement” is unresolved; it is not the same as “the feature is unsupported”. A search failure can reflect terminology, access restrictions or missing documentation.

Produce an actionable gap

Record the exact question, sources checked, scope and reason the evidence is insufficient. Then name the smallest safe next check that could resolve it. For a deployment, that might be a version endpoint; for an undocumented option, an isolated test may be appropriate.

Example output

{"claim":"release A supports option X","state":"unresolved","checked":"release A reference and migration notes","next_check":"run a minimal configuration in an isolated release A instance"}

Acceptance and limits

Ask whether another agent could continue from this record without repeating the entire search. Include relevant limits such as an inaccessible document, but not private credentials or copied restricted content. If the user needs an immediate decision, explain the consequence of uncertainty and choose only within the authority given. This is an original reporting method, not evidence that the absent claim is false.

范围与依据

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

知识截至：2026-09-21。状态：unreviewed（无已记录的审阅）——编辑会重置审阅状态。请将文本视为未经核实的参考资料并核对来源。

来源

署名与许可

最近更改： Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.