outputs

Language reference / outputs

Meaning and placement

document

The workflow’s return value · symmetric to inputs. Each entry is a ${{ tasks.X.output }} reference (untyped form · string) OR a typed declaration { value · type · description }. Powers nika run result + the output half of the callable-workflow schema.

Property	Declaration
Requirement	Optional in this object
Schema location	`/properties/outputs`
type	”object”
additionalProperties	{“anyOf”: [{“type”: “string”}, {“type”: “object”, “required”: [“value”], “additionalProperties”: false, “properties”: {“value”: {“type”: “string”}, “type”: {“ $ref": "#/$ defs/typeExpr”, “description”: “The output’s type · the full TypeExpr of 09-types (R3b · LAW-GRAMMAR-0211 · the flat 6-enum is dead alongside the inputs half · LAW-SURFACE-0211).”}, “description”: {“description”: “Free-form prose about this output · what a caller receives. Documentation only — the contract is `value` and `type`.”, “type”: “string”}}}]}

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

In a source template

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

illustration

        condition: "${{ with.has_findings }}"
        message: "Agent returned no findings, do not trust an empty run"   # SLOT

outputs:
  findings:
    value: ${{ tasks.execute.output.findings }}
    description: "The agent's typed findings"   # SLOT

Templates containing this field

Template	Source
`templates/agent-loop.nika.yaml`	Line 145
`templates/api-upload-and-create.nika.yaml`	Line 98
`templates/chain.nika.yaml`	Line 92
`templates/classify-and-route.nika.yaml`	Line 135
`templates/corpus-qa.nika.yaml`	Line 122
`templates/docker-report.nika.yaml`	Line 103
`templates/document-to-fields.nika.yaml`	Line 102
`templates/etl-state.nika.yaml`	Line 146
`templates/evaluate-and-optimize.nika.yaml`	Line 136
`templates/fanout.nika.yaml`	Line 182
`templates/gate-and-act.nika.yaml`	Line 78
`templates/human-gated-ship.nika.yaml`	Line 174
`templates/media-asset-pack.nika.yaml`	Line 121
`templates/website-brief.nika.yaml`	Line 104

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:outputs. Spec revision: c5ebbb7b862b. 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