让检查围绕任务、资料、例外与使用者展开，而不是围绕一个漂亮总分。
明确是资料检索、内容生成、任务分流还是页面体验。不同对象使用不同标准，不把视觉观感与业务可靠性混成一个结论。
保留问题、资料版本、使用角色与评估日期。输入改变后的结果应当记录为另一轮，而不是直接与旧条件下的结果比较。
答案正确、来源可查、范围正确和适当转人工，都是不同的结果要求。每项检查写清为什么重要，以及失败时影响哪个使用动作。
将内容错误、版本错误、缺失引用、交互失败和视觉问题分开，记录重现步骤与证据。问题清单应能够被具体处理。
修正后用相同条件重跑相关问题，同时检查相邻流程。不要只记录“已修改”，还要记录实际结果。
一组样例通过，说明这些样例在指定条件下通过，不自动证明所有情况。清楚的结论范围能让后续迭代更有依据。
Evaluate tasks, sources, exceptions and users rather than a flattering overall score.
Identify whether the object is retrieval, generation, routing or page experience. Different objects need different criteria; visual impression and operational reliability are not one conclusion.
Retain questions, source versions, user roles and evaluation dates. Results after input changes form a new run rather than being compared indiscriminately with older conditions.
Correct answers, inspectable references, correct scope and appropriate hand-offs are distinct requirements. Record why each matters and which user action is affected by a failure.
Separate content errors, version errors, missing references, interaction failures and visual problems. Record reproduction steps and evidence so each issue can be acted upon.
After a fix, repeat the relevant checks under the same conditions and examine adjacent flows. Record the result, not merely that a change was made.
Passing a set of examples means those examples passed under the stated conditions, not that every situation has been proven. A well-scoped conclusion supports further iteration.