Skip to main content
Live project control plane. The released engine discovers nika.yaml from the working directory toward its ancestors. The file is optional when built-in defaults are enough. Its project-shape grammar is closed: nika · ceiling · arm · traces · registry. Direct runs and the cadence path (nika arm · nika serve) read the same file.
nika.yaml governs the project around the SDK. A *.nika file carries one executable workflow. Keeping those roles separate is the foundation of a clean application integration.

One file for direct runs and armed beats

Every block is live, and they compose: direct runs apply the policy rungs, and nika arm, nika serve and nika arm fire read the same file. Leave out any block whose default suits the project. The closed project-shape vocabulary remains . An unknown key refuses with its line and the accepted set. A present file that silently ignores a typo would be more dangerous than an absent file, so the parser never drops one.

Discover the governing file

The engine walks from the current working directory toward its ancestors and uses the first nika.yaml, like Git finds .git.
DISCOVERY · FIRST PROJECT ROOT WINS
Prefer a cwd at the project root. It keeps workflow paths, project discovery and .nika/ state aligned. The CWD and monorepos page documents the split when a nested process room is intentional.

Found and inspect

A project file can be one line. nika arm validates the project file and its cadence grammar, reports its armed beats and schedules nothing. A direct run applies the same file’s policy rungs through the normal project discovery path. nika init also writes a commented nika.yaml, among about 30 agent, editor and hook files (the full list).
Do not pass nika.yaml to Nika.run(). The SDK runs a *.nika workflow. The engine discovers nika.yaml from cwd and applies its project policy around that run.

Continue through the project

Project file

Discovery, closed grammar and every rung in one file.

CWD and monorepos

Align project discovery, direct traces and armed state.

Arm registry

Cadence, spend, silence, overlap and suspension policy.

Policy ladders

Invocation, environment, project and operator precedence.

Runtime state

Traces, firing ledgers, watermarks and server persistence.