Skip to main content
The SDK is the application seam around a Nika workflow. Your product owns the request, interface and business state. Nika owns the workflow contract, the execution boundary and the receipt.
APPLICATION FLIGHT COMPUTER · TYPESCRIPT

​
Choose the surface

The two modules share a package, not a deployment assumption. Import the local module when the application and engine share a machine. Import the root module only when a compatible workflow service exists at the other end.

​
Install both halves

Then probe the actual binary:

​
The application loop

1

Anchor the project

Put nika.yaml at the project root and construct LocalNika with that working directory. The engine discovers project policy around every run.
2

Audit

Call check(). Findings resolve as typed data, so the interface can show the complete refusal instead of catching one opaque exception.
3

Admit

Read the cost floor, unbounded flag, permits and requirements. Product policy decides whether the clean workflow may run here.
4

Run

Stream events with run() or collect them with runToEnd(). Pass the caller’s cancellation signal and spend ceiling.
5

Keep the receipt

Store the trace identity beside business state. Verify the chain before treating a copied receipt as evidence.

​
Documentation graph

​
What the SDK does not own

  • It does not parse or enforce a second Nika language.
  • It does not turn an unpriced model into a zero-cost model.
  • It does not infer success from the last event a UI happened to recognize.
  • It does not turn the resident firer or local model endpoint into a workflow HTTP service.

Open the visual SDK map

The public site connects every guide to the language, workflows, boundary and proof registers.

Read the source

The package is Apache-2.0, zero dependency at runtime and tested against both local machine contracts and remote fixtures.