tasks

Language reference / tasks

Meaning and placement

document

The task map · the KEY is the task’s identity (snake_case · CEL-safe). Source order is presentation only — the graph alone schedules.

Property	Declaration
Requirement	Required in this object
Schema location	`/properties/tasks`
type	`"object"`
additionalProperties	declaration below

In the same object: const · inputs · model · nika · outputs · permits · run · secrets Schema source (use the pointer above)

In a source template

Excerpt from templates/agent-loop.nika, source lines 47–56. This is a fragment, not a runnable workflow.

illustration

  # two the agent may call. No `fs:` — see the note on `tools:` below.
  tools: ["nika:assert", "nika:done", "nika:jq"]

tasks:
  plan:
    infer:
      prompt: "Break '${{ inputs.goal }}' into at most 4 concrete steps."   # SLOT
      # SLOT: the spend ceiling for the planning call. Size it for the SEAT,
      # not for the answer: a reasoning model spends tokens thinking before
      # it emits the first brace, and a ceiling that cuts it off mid-thought

Templates containing this field

Template	Source
`templates/agent-loop.nika`	Line 50
`templates/aggregate-by-key.nika`	Line 25
`templates/api-upload-and-create.nika`	Line 67
`templates/bounded-batch.nika`	Line 23
`templates/chain.nika`	Line 45
`templates/classify-and-route.nika`	Line 75
`templates/corpus-qa.nika`	Line 30
`templates/deduplicate-records.nika`	Line 25
`templates/docker-report.nika`	Line 44
`templates/document-to-fields.nika`	Line 36
`templates/etl-state.nika`	Line 61
`templates/evaluate-and-optimize.nika`	Line 37
`templates/fanout.nika`	Line 81
`templates/gate-and-act.nika`	Line 50
`templates/human-gated-ship.nika`	Line 84
`templates/media-asset-pack.nika`	Line 50
`templates/parallel-review.nika`	Line 51
`templates/project-public-fields.nika`	Line 26
`templates/recover-optional-file.nika`	Line 24
`templates/snapshot-diff.nika`	Line 24
`templates/validate-records.nika`	Line 23
`templates/website-brief.nika`	Line 46

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:tasks. Spec revision: 5c40ba456c53. How documentation stays connected.

YAML

Language fields

CLI & errors

Data catalogs

Workspace

Documentation system

Tool contracts

Meaning and placement

document

In a source template

Templates containing this field

Contract and implementation

​Meaning and placement

​document

​In a source template

​Templates containing this field

​Contract and implementation

Meaning and placement

document

In a source template

Templates containing this field

Contract and implementation