nika
Meaning and placement
document
The file’s NAME · kebab-case · and the mark that says « this is a nika file ». One word, one meaning across both document types:nika.yaml carries the PROJECT name, a *.nika carries the WORKFLOW name. The document TYPE is read from tasks: — present means workflow, absent means project — so it survives a blob, a paste or an HTTP body where the filename does not travel. This key held the literal v1 until the envelope nuke; it carried zero bits as a version (there is no nika: v2 — ever) and now carries the file’s most necessary field instead. A retired version tag (v1, v2, …) is refused here as in the project file: the name is a word, never a version (NIKA-PARSE-003).
In the same object: const · inputs · model · outputs · permits · run · secrets · tasks
Schema source (use the pointer above)
In a source template
Excerpt fromtemplates/agent-loop.nika, source lines 24–33. This is a fragment, not a runnable workflow.
illustration
Templates containing this field
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:nika. Spec revision: 5c40ba456c53.
How documentation stays connected.