executor.json 1.83 KB
{
  "id": "executor",
  "label": "执行型 org node 的 work graph(串行起手式)",
  "whenToUse": "宿主 org node 的职能是「按上游给的约束做出实际产物」,且这次任务小到不值得拆并行分支时用本骨架——典型是 org-coder / org-writer / org-monitor。典型信号词:实现、写、改、跑、部署,且任务是单一交付物。三节点:做 → 自测 → 本层验收,自测和验收失败都退回实现节点。任务能明显拆成多个互不依赖的分支时改用 executor-fanout.json;宿主是规划类节点用 planner.json;宿主是 org-validator 用 validator.json。",
  "ownerOrgNode": "{{orgNode}}",
  "dataContractNotes": "交付物走 artifact,自测记录走 log。validator 既要看测试记录(紧邻上游 produces log)也要看被验的交付物本身,而交付物的产出方隔了一个节点,所以用 needs artifact 中继——这条就是 tools.md §6bis 举的那个例子。上游给的 sdd 与验收标准 acceptance 都由别的 org node 的图产出,属任务级共享,引擎按 task + kind 自动递,不在本图沿边声明。",
  "nodes": [
    { "nodeName": "{{orgNode}}-impl", "systemAgentId": "{{implAgent}}" },
    { "nodeName": "{{orgNode}}-test", "systemAgentId": "{{testAgent}}" },
    { "nodeName": "{{orgNode}}-validator", "systemAgentId": "{{validatorAgent}}" }
  ],
  "edges": [
    { "from": "{{orgNode}}-impl", "to": "{{orgNode}}-test", "condition": "success", "produces": ["artifact"] },
    { "from": "{{orgNode}}-test", "to": "{{orgNode}}-validator", "condition": "success", "produces": ["log"], "needs": ["artifact"] },
    { "from": "{{orgNode}}-test", "to": "{{orgNode}}-impl", "condition": "fail", "edgeKind": "backward" },
    { "from": "{{orgNode}}-validator", "to": "{{orgNode}}-impl", "condition": "fail", "edgeKind": "backward" }
  ]
}