validate-bug

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Validate Bug

验证漏洞

When to Use

使用时机

Use after
reproduce-bug
has supplied a finding and PoC package. Read the record contract. Before target commands, follow its project guidance.
在
reproduce-bug
提供 finding 和 PoC 包后使用。阅读记录契约。 执行目标命令前,遵循其项目指导。

When NOT to Use

不适用的场景

Do not use to repair a PoC, develop a patch, or infer reproduction from the reproducer's narrative.
不要用于修复 PoC、开发补丁,或根据复现者的叙述推断是否可以复现。

Procedure

操作步骤

  1. Read
    finding.json
    , the reproduction's proof type, commands, any PoC, and raw receipts. Do not read the reproducer's transcript.
  2. Rerun the same baseline compiler command for compile failures, or rebuild and rerun the unchanged runtime PoC and planned scoped inputs. Save stdout, stderr, exit status and timing in
    validate/receipts/
    . If an observation is unreliable, return
    inconclusive
    instead of inferring either presence or absence.
  3. Decide whether the target diagnostic or runtime assertion demonstrates the exact claim and violates the stated invariant. Write
    validate.json
    as
    confirmed
    ,
    not_confirmed
    , or
    inconclusive
    with a short reason and agent identity.
    Validate record schema:
json
{
  "schema_version": 1,
  "outcome": "confirmed",
  "agent": "validator-1",
  "reason": "The unchanged PoC reached the assertion and demonstrated the claim."
}
  1. Manifest the complete
    validate/
    directory with
    uv run --no-project <script> manifest <validate-step-dir>
    , then run the record checker. Return the package without editing the PoC or finding.
  1. 读取
    finding.json
    、复现的证明类型、命令、任何 PoC 以及原始回执。 不要读取复现者的对话记录。
  2. 对于编译失败,重新运行相同的基线编译器命令;或者重新构建并重跑未更改的运行时 PoC 和计划范围内的输入。将 stdout、stderr、退出状态和耗时保存到
    validate/receipts/
    。如果观察结果不可靠,应返回
    inconclusive
    ,而不是推断问题存在或不存在。
  3. 判断目标诊断信息或运行时断言是否证明了确切主张,并违反了既定不变量。将
    validate.json
    写为
    confirmed
    、
    not_confirmed
    或
    inconclusive
    ,并附上简短原因和 Agent 身份。
    验证记录 Schema:
json
{
  "schema_version": 1,
  "outcome": "confirmed",
  "agent": "validator-1",
  "reason": "The unchanged PoC reached the assertion and demonstrated the claim."
}
  1. 使用
    uv run --no-project <script> manifest <validate-step-dir>
    为完整的
    validate/
    目录生成清单,然后运行记录检查器。返回该包,不编辑 PoC 或 finding。

Rationalizations to Reject

需要拒绝的捷径

ShortcutRequired action
Fix the PoC to make the claim work.Mark it inconclusive and explain why.
Trust the reproducer's conclusion.Rerun the unchanged package independently.
捷径必须采取的操作
修改 PoC 以使主张成立。标记为 inconclusive 并解释原因。
信任复现者的结论。独立重跑未更改的包。