GateAnswer

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/usestring-ai/json-schema/usestring-ai-gate-answer-schema.json",
  "title": "GateAnswer",
  "description": "One gate resolution. EXACTLY ONE member may be set, and which member is set picks the answer kind — there is no `kind` property, deliberately: a discriminator that can disagree with its payload is a second thing to validate and a way for a caller to be coerced onto an arm they did not fill in. Setting more than one member is a 400 (`gate_answer_ambiguous`); setting none is a 400 (`gate_answer_required`).\n\n`text` IS THE ESCAPE HATCH: a plain {\"text\": \"...\"} is a valid answer to EVERY gate kind, including kinds that did not exist when your client was generated. The brain raises kinds dynamically and new ones appear without a version bump, so a client that meets a `kind` it has no renderer for should show the gate's `prompt` and send the operator's typed reply as `text` rather than failing the build.\n\nAn answer whose member does not match the gate's kind is refused by the core with a 400. This API does not know the gate's kind and never guesses one.",
  "x-generated": "2026-10-31",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/feedbuilder-usestring-ai-openapi.yaml#/components/schemas/GateAnswer",
  "oneOf": [
    {
      "additionalProperties": false,
      "properties": {
        "choice_id": {
          "type": "string"
        }
      },
      "required": [
        "choice_id"
      ],
      "title": "choice_id",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "confirm": {
          "type": "boolean"
        }
      },
      "required": [
        "confirm"
      ],
      "title": "confirm",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "schema": {
          "$ref": "#/$defs/SchemaReviewAnswer"
        }
      },
      "required": [
        "schema"
      ],
      "title": "schema",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "text": {
          "description": "A free-text answer. Valid against EVERY gate kind — this is the escape hatch for kinds your client does not recognise.",
          "type": "string"
        }
      },
      "required": [
        "text"
      ],
      "title": "text",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "source": {
          "$ref": "#/$defs/SourcePickerAnswer"
        }
      },
      "required": [
        "source"
      ],
      "title": "source",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "publish": {
          "$ref": "#/$defs/PublishReviewAnswer"
        }
      },
      "required": [
        "publish"
      ],
      "title": "publish",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "initial_query": {
          "type": "string"
        }
      },
      "required": [
        "initial_query"
      ],
      "title": "initial_query",
      "type": "object"
    },
    {
      "additionalProperties": false,
      "properties": {
        "questionnaire": {
          "$ref": "#/$defs/QuestionnaireAnswer"
        }
      },
      "required": [
        "questionnaire"
      ],
      "title": "questionnaire",
      "type": "object"
    }
  ],
  "$defs": {
    "PublishReviewAnswer": {
      "properties": {
        "approve": {
          "description": "REQUIRED. Send `true` or `false` explicitly. A body that OMITS this key is refused with 400 `approve_required`; it is never read as `false`. A silent `false` here withholds a FINISHED FEED and ends the run — the single most expensive way for a client bug to be invisible. If your generated client models this as a plain boolean defaulting to false, fix the client. `null` earns the same 400, so the member is typed as a plain boolean and not a nullable one.",
          "type": "boolean"
        },
        "cadence": {
          "type": "string"
        },
        "delivery_target": {
          "items": {
            "type": "string"
          },
          "type": "array"
        },
        "notes": {
          "type": "string"
        }
      },
      "required": [
        "approve"
      ],
      "type": "object"
    },
    "QuestionnaireAnswer": {
      "properties": {
        "answers": {
          "additionalProperties": {
            "type": "string"
          },
          "description": "Keyed by `Question.id`. A question you are SKIPPING must be ABSENT, never present with an empty value — the brain has to be able to tell a skip from an answer. At least one entry is required on a request.",
          "type": "object"
        }
      },
      "required": [
        "answers"
      ],
      "type": "object"
    },
    "SchemaColumnEdit": {
      "properties": {
        "drop": {
          "description": "Omitted means KEEP the column — the non-destructive default. That is the opposite of `approve`, whose omitted default would be the destructive one, which is why `approve` is refused when absent and this is not.",
          "type": "boolean"
        },
        "key": {
          "type": "string"
        },
        "rename_to": {
          "type": "string"
        },
        "required": {
          "type": "boolean"
        }
      },
      "required": [
        "key"
      ],
      "type": "object"
    },
    "SchemaReviewAnswer": {
      "properties": {
        "approve": {
          "description": "REQUIRED. Send `true` or `false` explicitly. A body that OMITS this key is refused with 400 `approve_required`; it is never read as `false`. The field is presence-tracked on purpose: a silent `false` at a review gate is not \"unanswered\" but a considered refusal that withholds the work and ends the run, with nothing recording that nobody decided. If your generated client models this as a plain boolean defaulting to false, fix the client — an absent decision must never reach this API as a decline. `null` is not an escape either: it earns the same 400, which is why this schema types the member as a plain boolean rather than a nullable one.",
          "type": "boolean"
        },
        "edits": {
          "items": {
            "$ref": "#/$defs/SchemaColumnEdit"
          },
          "type": "array"
        },
        "notes": {
          "type": "string"
        }
      },
      "required": [
        "approve"
      ],
      "type": "object"
    },
    "SourcePickerAnswer": {
      "properties": {
        "chosen_url": {
          "description": "Set exactly one of `chosen_url` or `re_discover`. Both, or neither, is a 400 (`source_answer_ambiguous`).",
          "type": "string"
        },
        "re_discover": {
          "type": "boolean"
        }
      },
      "type": "object"
    }
  }
}