Skip to main content

​
What can I install?

The SDK bundles a native engine and requires Node.js 22 or newer. Its package version is a separate publication from the CLI. A merged SDK change or a newer engine release does not update an installed npm package.
Start with the SDK if you are adding workflows to an app. Start with the CLI if you want to check and run a .nika file from your terminal.

​
What does the engine snapshot prove?

The engine fields below are projected from one selected published stable release. The installer verifies its checksums and attestation; the projector checks the binary’s reported version and build against that release’s tag before writing. The publication date is not the date of the last website build. For the full inventory, including release records with no attached assets, see Releases.

​
Language facts have a different owner

The specification supplies verbs, builtins and skeletons through the shared canon projection. Its named providers describe the language contract; the engine’s catalog can contain additional adapters. See Providers and Sources and synchronization. Crate totals, test totals, architectural decisions and work on engine main are development records. They do not prove that a feature is in the binary you download. The roadmap keeps future work separate from releases.

​
How updates reach these pages

The hourly release sync collects published stable releases, verifies the selected native release, and projects both the release index and the engine snapshot. It proposes the generated files, dispatches the documentation checks, and merges only after those checks and normal branch protection permit it. Mintlify then deploys main. The native snapshot updates version, engineSha, providers, firstCommand and lastUpdated together. It does not rewrite historical development counts, publish an npm package, or turn a roadmap proposal into a released feature. Failed validation leaves the previous documentation in place and a failed sync run to investigate. For contributors, run these commands from the documentation repository with the verified release selected through NIKA_BIN:

​
Find the right record

Releases

Published versions, dates, notes and attached downloads.

Roadmap

What is available and what still needs release evidence.

Historical milestones

Original dated accounts, preserved with their historical context.

Timeline and evidence

How to distinguish a release, a proposal and a historical account.