validator.json 1.5 KB

Edit Raw Blame History



1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

{
  "id": "validator",
  "label": "org-validator 的 work graph（归因排第一位）",
  "whenToUse": "宿主 org node 是 org-validator（org graph 末端那个「整个任务达成了吗」的节点）时**必须**用本骨架。它与另外两个骨架的硬性区别：第一个节点必须是归因节点 validator-reflection——先归因、再决定后面怎么验/怎么退（27-P3/P4 §四.D.3）。它产出的 fail_reason + remediation_note 会透传回 org 层，成为 org graph 选走哪条 fail 边的唯一依据（§四.D.0 三值透传 / §四.D.2.2 选边）。少了这个节点，org 层失败后不知道该退回 org-planner 还是 org-coder。宿主不是 org-validator 就别用本骨架。",
  "ownerOrgNode": "org-validator",
  "nodes": [
    { "nodeName": "validator-reflection", "systemAgentId": "validator-reflection" },
    { "nodeName": "benchmark-validator", "systemAgentId": "benchmark-validator", "readsArtifacts": ["goal-benchmark.json"] },
    { "nodeName": "testdata-validator", "systemAgentId": "testdata-validator", "readsArtifacts": ["goal-test-data/"] }
  ],
  "edges": [
    { "from": "validator-reflection", "to": "benchmark-validator", "condition": "success" },
    { "from": "benchmark-validator", "to": "testdata-validator", "condition": "success" },
    { "from": "benchmark-validator", "to": "validator-reflection", "condition": "fail", "edgeKind": "backward" },
    { "from": "testdata-validator", "to": "validator-reflection", "condition": "fail", "edgeKind": "backward" }
  ]
}