The mark
nika: <name>, the first line of every workflow. The key nika declares
“this is a Nika document”, the value is the workflow’s own kebab-case
identifier — there is no version to pin and no separate schema: or
apiVersion: field (the engine’s internal canonical URI stays
https://nika.sh/spec/v1 for RDF / conformance tooling, but the author
never types a URL). A tasks: key makes the document a workflow; the
project file nika.yaml (no tasks:) names the project
(nika: my-project), not a schema tag.
Point your editor
Add the LSP modeline at the top of any.nika so your editor’s YAML
language server consumes the JSON Schema directly:
the modeline · paste at the top of any workflow
Local validation
nika spec --schema prints
the exact one your binary enforces, and nika check remains the judge.
Versioning policy
- The envelope carries no version marker — the mark is the name.
- Minor additions (a new optional field, a new builtin) are additive.
- A grammar change ships with its
nika check --fixmigration and a refusal that names the move. 0.124 addsimages:(anagent:task on a harness seat) andnika:image_composeadditively. - Anti-pattern:
nika: v1+workflow: { id }— the previous envelope (through 0.108);nika check --fixmoves the id ontonika:.