nvidia-production-f205.up.railway.app

resolve_decision

Record the outcome of a branching step: which edge was taken and why. REQUIRED before moving past a step with branches — get_process_progress will not offer anything beyond an unresolved decision. The engine uses the assignee’s submitted task values for branch criteria, including dropdown choices (e.g. shippingMethod equals Courier). Read get_process_map first. Only pass measurements when you have additional real evidence; never replace submitted values. For example, numeric measurements may be {"testPassRate": 100, "openCriticalIssues": 0}; the engine verifies them and REFUSES the branch on any violation (evidence_conflict) — then ask the human whether the measurements are wrong or whether to take the failure branch, never how to override. Choosing a loop-back branch re-opens those steps.

Input schema

{
  "type": "object",
  "properties": {
    "stepId": {
      "type": "string"
    },
    "branchTo": {
      "type": "string"
    },
    "reason": {
      "type": "string"
    },
    "evidence": {
      "type": "string",
      "description": "Free-text context (optional)"
    },
    "measurements": {
      "type": "object",
      "description": "Structured measured values checked against the edge criteria, e.g. {\"testPassRate\": 100, \"openCriticalIssues\": 0, \"rollbackReady\": true}"
    }
  },
  "required": [
    "stepId",
    "branchTo",
    "reason"
  ]
}