extract

Language reference / extract

Meaning and placement

task

Named jq-expression bindings extracted from the verb’s raw response · read downstream as ${{ tasks.X.<name> }}. The field names the OPERATION (run this jq); it does not write output — ${{ tasks.X.output }} stays the raw response (spec/03-dag.md §extract). jq is the single data extraction-and-transform language (the former RFC 9535 JSONPath was dropped · jq is a superset · per spec/04-variables.md §216-225). A binding may not shadow a record projection: output · status · error · started_at · ended_at · duration_ms are forbidden at parse time (spec/04-variables.md §Rules) — enforced via propertyNames.

Property	Declaration
Requirement	Optional in this object
Schema location	`/$defs/task/properties/extract`
type	”object”
additionalProperties	{“type”: “string”, “format”: “jq”}

In the same object: after · agent · exec · for_each · group · infer · invoke · lift · on_error · retry · returns · timeout · when · with Schema source (use the pointer above)

In a source template

Excerpt from templates/document-to-fields.nika.yaml, source lines 51–60. This is a fragment, not a runnable workflow.

illustration

        condition: ${{ size(with.document) > 0 }}
        message: "Document is empty after whitespace is trimmed"

  extract:
    with:
      document: ${{ tasks.normalize_document.output }}
    after:
      document_nonempty: success
    infer:
      max_tokens: 600                # SLOT: extraction spend ceiling

Templates containing this field

Template	Source
`templates/document-to-fields.nika.yaml`	Line 54
`templates/gate-and-act.nika.yaml`	Line 58

These are literal key occurrences in the source files, not an execution or conformance claim. How to instantiate a template.

Contract and implementation

This page projects the named specification revision. Check released engine status and the validation workflow before running a file. An optional field is not evidence that every engine supports every value. Canonical identity: language:word:extract. Spec revision: c5ebbb7b862b. How documentation stays connected.

YAML

Language fields

CLI & errors

Data catalogs

Workspace

Documentation system

Tool contracts

Meaning and placement

task

In a source template

Templates containing this field

Contract and implementation

​Meaning and placement

​task

​In a source template

​Templates containing this field

​Contract and implementation

Meaning and placement

task

In a source template

Templates containing this field

Contract and implementation