const

Language reference / const

Meaning and placement

document

Named constants · ${{ const.X }} · a fixed value baked into the workflow. Either a bare literal, or a { type, value } typed constant whose value: MUST conform to type:. The literal half of the dead vars: block (R3a · LAW-SURFACE-0201) · everything that is not required: true lands here per the E-split total rule.

Property	Declaration
Requirement	Optional in this object
Schema location	`/properties/const`
type	”object”
additionalProperties	{“type”: [“string”, “number”, “boolean”, “array”, “object”, “null”], “if”: {“type”: “object”, “required”: [“type”, “value”]}, “then”: {“additionalProperties”: false, “properties”: {“type”: {“ $ref": "#/$ defs/typeExpr”}, “value”: {“description”: “The constant value · MUST conform to `type:` (NIKA-DEFAULT-001).”}, “description”: {“description”: “Free-form prose about this constant · why the value is what it is. Documentation only — the contract is `type` and `value`.”, “type”: “string”}}, “$comment”: “An object carrying BOTH `type` and `value` is a typed constant · the type speaks the full TypeExpr (R3b) and values_core checks the value against it (NIKA-DEFAULT-001) · an object missing either key is a bare literal object constant.”}}

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

In a source template

Excerpt from templates/api-upload-and-create.nika.yaml, source lines 36–45. This is a fragment, not a runnable workflow.

illustration

# Run · nika run <file>          # offline rehearsal · no key exported
nika: api-upload-and-create-template       # SLOT: kebab-case workflow id

const:
  api_base: "https://api.example.com"     # SLOT: the product API base
  asset_path: "./out/assets/asset-1.png"  # SLOT: the file to upload

secrets:
  API_KEY:
    source: env

Templates containing this field

Template	Source
`templates/api-upload-and-create.nika.yaml`	Line 39
`templates/chain.nika.yaml`	Line 32
`templates/classify-and-route.nika.yaml`	Line 20
`templates/corpus-qa.nika.yaml`	Line 21
`templates/document-to-fields.nika.yaml`	Line 21
`templates/etl-state.nika.yaml`	Line 50
`templates/evaluate-and-optimize.nika.yaml`	Line 33
`templates/fanout.nika.yaml`	Line 63
`templates/gate-and-act.nika.yaml`	Line 28
`templates/human-gated-ship.nika.yaml`	Line 56
`templates/media-asset-pack.nika.yaml`	Line 35
`templates/website-brief.nika.yaml`	Line 37

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:const. 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