Parameters
Configure the work using the Generation node reference. The authoring form uses
Field objects in place of field IDs.Entity bindings
Generation and Quorum use the following properties for each input or output entity.One of the supported values:
JUDGEMENT, EXPLANATION, PROMPT, USER_PROMPT, RESPONSE, RESPONSE_EVALUATION, RUBRIC, RUBRICS_GROUP, DIALOG, DIALOG_STEP, DIALOG_EVALUATION, SHORT_ANSWER, FEEDBACK, CONTEXT, IMAGE, ANNOTATION, SINGLE_LABEL, MULTI_LABEL, VIDEO, DOCUMENT, GOLDEN_SET, LOGS, SOLUTION, CODE, METADATA, AUDIO, AGENT_TRAJECTORY, MCP_SERVER, CONTAINER, or CUSTOM.Path used to extract the entity value. Dynamic entities require exactly one
[*] wildcard; static entities cannot use that wildcard.Relations to other entities, using
field and rel_type. For example, { field: prompt, rel_type: "references" } relates an output to its prompt. See the node reference for relation behavior.Choices for label entities. Output entities with
entityType: "SINGLE_LABEL" or "MULTI_LABEL" require at least two entries.Whether this binding represents multiple entity values. A dynamic entity’s field needs an array JSON schema.
For
dynamic: true, supply an integer from 1 to 50. The SDK type permits omission or null, but platform validation requires the bound. When dynamic is false or omitted, only null or omission is allowed.