Guide contents

study_batch_submit

Purpose and availability

Build only: atomically queue 1–8 explicitly selected exact case versions. Queue capacity and candidate ownership are validated before any submission.

Before invocation

Inspect the current definition and exact version/project binding before invoking. Required fields, enums, bounds and consent fields below are authoritative. Omit no required input and do not invent unavailable values.

Exact input schema

{
  "additionalProperties": false,
  "properties": {
    "cases": {
      "items": {
        "additionalProperties": false,
        "properties": {
          "case_id": {
            "maxLength": 256,
            "minLength": 1,
            "type": "string"
          },
          "version": {
            "pattern": "^[a-f0-9]{64}$",
            "type": "string"
          }
        },
        "required": [
          "case_id",
          "version"
        ],
        "type": "object"
      },
      "maxItems": 8,
      "minItems": 1,
      "type": "array"
    }
  },
  "required": [
    "cases"
  ],
  "type": "object"
}

Results, errors and safety

Inspect the structured result and retained IDs/artifacts. Errors, unsupported profiles, missing data and cancellation remain explicit. A successful call grants no human engineering approval. Do not retry inference automatically. See Workflows, History and Project tools.