Skip to main content
This page exists because a word you cannot define is a wall. Each entry is one sentence and a pointer to the page that owns the idea — the definition lives there, this is only the door.

The file

Envelope — the top-level keys a workflow file may carry, and only those: nika · model · inputs · const · secrets · permits · run · tasks · outputs. Nine keys, closed. Anything else is refused by name. → Workflows nika: — the first line of every Nika file. The key says this is a Nika file; the value is the file’s name, kebab-case. It is not a version, and there is no nika: v2. → YAML syntax Workflow vs project file — a document with a tasks: key is a workflow; a document without one is a project file (nika.yaml, which carries settings like a spend ceiling). The rule is the presence of tasks:, never the filename — so it still holds for a file pasted into a chat or piped on stdin, where the .nika suffix is gone. → YAML syntax Task — one named unit of work, declaring exactly one of the four verbs (infer · exec · invoke · agent). → Verbs

The graph

DAG — directed acyclic graph: the shape your tasks form once their dependencies are drawn. Acyclic means no task may wait, however indirectly, on itself. → Workflows Wave — a scheduling layer. Every task whose dependencies are already satisfied runs in the same wave, in parallel. nika check prints the wave plan before anything runs, so 3 waves · 5 tasks means five tasks arranged into three rounds. → Workflows with: and after: — the two edge kinds. with: is a data edge (a task reads another’s output); after: is a control edge (a task waits, without reading). → Bindings unwind — a cleanup edge on a producer that started. Spec 03-dag: the unwind task runs after that producer, success or failure. A producer that never started has no cleanup. A terminal report task (after: {x: terminal}) is a different edge — it is not unwind. → Workflows · Cleanup

The expressions

CEL — Common Expression Language, the small expression language ${{ … }} speaks, and the language of a when: condition. It is not a template engine and not shell: it evaluates an expression and gives back a value. → Bindings jq — the query language used to pull a field out of a result or reshape one: in extract: bindings, the nika:jq builtin and nika:fetch’s mode: jq, never inside ${{ }} or outputs: (those are CEL). Same jq as the command-line tool. → Bindings

Safety and cost

permits: — the declared boundary of what a run may touch: which paths it may read or write, which hosts it may reach, whether it may execute. An absent permits: block is zero authority, never a default allowance. → Security Blast radius — everything a run could touch if it went wrong, read off the declared permits: before the run starts rather than discovered after. → Security Lethal trifecta — three grants that are each ordinary alone and dangerous together: access to private data, an untrusted input, and a way out to the network. When a workflow has all three and the untrusted content can actually reach the way out, nika check refuses it (NIKA-SEC-009) unless a human gate stands in the path. → Security mock/echo — the test model. It needs no provider, no API key and no network, and it costs nothing, so a workflow can be rehearsed end to end before any real model is named. → Providers Access path — how Nika reaches a model: a local server, a provider API with your key, or an agent app you are signed into (a harness seat). The model is in the file; the access path is chosen on the machine. → Providers · Model and access

Records and process

Trace — the record a run leaves: one NDJSON file (one JSON object per line) holding what ran, in what order, and at what cost, hash-chained so a later edit is visible. → Traces Seal — a run’s record signed with the machine’s run-signing key. A sealed trace verifies as SEALED; an unsigned one is intact but UNSEALED. → Seal your runs Receipt — the engine-issued pointer to a run’s record that the SDK hands your code; traceVerify(receipt) asks the engine to check it. → Receipts Hint — advisory output from nika check, named like native-first/002. A hint never fails your check on its own; --native-strict is the flag that promotes the native-first family to a failure. → Machine surfaces NEP — Nika Enhancement Proposal, the numbered process by which the language changes. A NEP-00NN reference in output points at the proposal that introduced the rule you just met.

The TypeScript SDK

Admission — the engine’s check before a run starts. Refused: the SDK’s run() throws and no run exists. Admitted: you get a run handle. → How the SDK works Run, job, execution — a run is this client’s handle on one admitted workflow (run.id); over HTTP the same id names the server’s durable job; an execution is the engine’s own id for what ran (execution_id). → How the SDK works Settlement — how a run ended: its status, cause, task tally and spend (result.settlement). → Results Served name — a workflow’s path from a nika serve project root, such as workflows/hello.nika. → Server quickstart Resident — a running nika serve process. → Resident server Session — the conversation bare nika opens on a terminal: describe a job, review the proposed file, save it, run it. → The terminal Session

Coming from somewhere else

If your reflexes are GitHub Actions or Kubernetes, the mapping is short: → How Nika compares