value

Meaning and placement

The constant value · MUST conform to type: (NIKA-DEFAULT-001).

Property	Declaration
Requirement	Optional in this object
Schema location	`/properties/const/additionalProperties/then/properties/value`

In the same object: description · type Schema source (use the pointer above)

The schema declares this field at the location below.

Property	Declaration
Requirement	Required in this object
Schema location	`/properties/outputs/additionalProperties/anyOf/1/properties/value`
type	”string”

In the same object: description · type Schema source (use the pointer above)

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

illustration

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

Template	Source
`templates/agent-loop.nika.yaml`	Line 147
`templates/classify-and-route.nika.yaml`	Line 65
`templates/docker-report.nika.yaml`	Line 105
`templates/document-to-fields.nika.yaml`	Line 80
`templates/etl-state.nika.yaml`	Line 148
`templates/gate-and-act.nika.yaml`	Line 59

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

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:value. Spec revision: c5ebbb7b862b. How documentation stays connected.