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.
The SDK does not replace project policy. It supplies the invocation rung and the working directory that lets the engine discover the rest.

Run spend

SPEND LADDER · CLOSEST EXPLICIT DECISION WINS
maxCostUsd is invocation-specific. Keep the project default in nika.yaml instead of copying it into every application call.

Trace retention

The matching NIKA_TRACE_* environment knob wins over the project retention rung, then the engine default applies. This lets an immutable project run under different operational retention obligations.

Registry provenance

The project floor max-composes with the operator policy under ~/.nika. A repository can demand stronger provenance. It cannot weaken the machine owner’s floor.
In 0.124.3 a first fetch of a registry: coordinate is refused (NIKA-REG-005) whatever the floor says: take the workflow file from the registry repository and use it by path (Known limits).

Keep one owner per decision

Do not create an application nikaConfig object that mirrors every project key. That produces a second control plane with no precedence contract. Construct Nika once with cwd; pass only invocation-specific inputs, model and ceiling per run. Cancellation is the separate run.cancel() verb.

Continue

SDK configuration

Constructor and call-level options.

Security boundary

Permits, secrets, argv and cancellation.

Project file

The closed grammar behind these ladders.

Arm registry

Per-tick money and missed-run policy.