adjudicate-regression

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Adjudicate evidence

证据裁决

When to Use

何时使用

Input: candidate, frozen sources, available reproduction/replay packages and registry assignment. Use a fresh context distinct from the reproducer and replayer. Early exclusions may lack experiments. Follow project guidance before target work.

输入：候选问题、冻结的源代码、可用的复现/重放包和注册表分派。使用与 reproducer 和 replayer 不同的全新上下文。早期排除项可能缺少实验。在开始目标工作前，遵循项目指导。

When NOT to Use

何时不要使用

Producing missing evidence; return the gap to the caller.

不要用于生成缺失证据；应将证据缺口返回给调用方。

Decide

裁决

Read the standard, labels and file contract. Verify seals. Inspect source, setup, PoC, actual logs and security assumptions, not only summaries.
Identify the claimed defect and assess whether the change introduced it. Rule out incomplete fixes, latent/pre-existing bugs, intentional changes, unsupported expectations and unreachable scenarios with cited evidence. Establish attacker access and applicable protections for security findings.
Confirm only when reproduction and independent replay ran the same PoC/input against live S0/S1 through real interfaces, showing correct behavior before and failure afterward. Explain supported behavior, reachability and patch causality. Assign severity/likelihood with reasons.
Otherwise select an evidenced exclusion or
```
UNRESOLVED
```
; state what remains unproved. For
```
UNRESOLVED
```
, put the standard's concise paragraph separating observed gaps, plausible explanations and resolving checks in
```
reason
```
so reports retain it. Incomplete fixes and existing bugs stay outside regression totals. Check known findings/issues/PRs before claiming novelty; report unknown if unavailable.
For requested deduplication, establish whether supplied candidates share a root cause. Preserve change mappings; never deduplicate unresolved claims into confirmation.
Write and seal
```
decision.json
```
; cite evidence for every conclusion. Record any blocker preventing adjudication.

阅读标准，标签和文件契约。核验封存状态。检查源代码、 setup、PoC、实际日志和安全假设，而不只是摘要。
确定所声称的缺陷，并评估变更是否引入了该缺陷。根据所引用的证据，排除不完整的修复、潜在/既有 bug、有意变更、缺乏依据的预期和不可达场景。对于安全类发现，明确攻击者访问权限和适用的防护措施。
只有当复现和独立重放通过真实接口针对实时 S0/S1 运行了相同的 PoC/输入，并显示变更前行为正确、变更后失败时，才确认该问题。说明受支持的行为、可达性和补丁因果关系。评定严重性/可能性，并说明理由。
否则，作出有证据支持的排除判定，或标记为
```
UNRESOLVED
```
；说明哪些内容仍未得到证明。对于
```
UNRESOLVED
```
，按照标准在
```
reason
```
中填写一段简洁说明，区分已观察到的缺口、可能的解释以及为解决疑问所需进行的检查，以便报告保留该说明。不完整的修复和既有 bug 不计入回归总数。在声称具有新颖性之前，检查已知的发现、问题和 PR；如果无法获取这些信息，则报告为未知。
按要求进行去重时，确定所提供的候选项是否具有共同的根因。保留变更映射关系；绝不将未解决的主张去重后转为确认结果。
编写并封存
```
decision.json
```
；为每项结论引用证据。记录任何阻碍裁决的阻塞因素。

Report Back

报告返回

Keep detailed reasoning in the sealed package. Return only:

Status:
```
complete
```
or
```
blocked
```
, matching the record.
Record: sealed
```
decision.json
```
path, or why none was produced.
Result: outcome and one-sentence reason.
Gap: missing evidence or required caller action, if any.

A completed decision may be

UNRESOLVED

; task status and finding outcome differ.

将详细推理保留在封存包中。仅返回：

状态：
```
complete
```
或
```
blocked
```
，与记录一致。
记录：已封存的
```
decision.json
```
路径，或说明未生成该文件的原因。
结果：裁决结果及一句话理由。
缺口：如有，列出缺失的证据或调用方需要采取的行动。

已完成的裁决可以是

UNRESOLVED

；任务状态与发现结论并不相同。

Rationalizations to Reject

应拒绝的理由

“S0 passes and S1 fails”: exposing an existing defect is a latent bug.

“S0 通过且 S1 失败”：暴露既有缺陷属于潜在 bug。