Skip to main content
docs.nika.sh is the home of Nika documentation: installation, workflow authoring, language references, SDK guides and architecture. nika.sh is the product site. Keep documentation bookmarks on this domain.

​
The path, in order

1

Get a first result

Introduction → SDK quickstart → project setup. Five minutes inside your own app: install the npm package, save one file, run it, read typed outputs — no key, no server, no CLI install needed for local runs.
2

Prefer the terminal?

The CLI runs the same files: install → first workflow. Same engine, same trace.
3

Learn the mechanics

Workflows · verbs · bindings · traces · security — one concept at a time, after you have a result in hand.
4

Ship a real job

Examples from starter to multi-step · patterns for the writing discipline · cost honesty before a paid model.

​
Find a specific reference

Use the current documentation destination when following an older bookmark. For example, the reference formerly at /language/stdlib/assert is now the assert reference; /templates opens the template guide. A general category guide is labeled as a guide, rather than presented as the exact reference for an individual object. An old bookmark on the product website is not proof that a redirect has been deployed there. Use the documentation destination directly. Machine endpoints such as the install script and schema URLs are separate public contracts; moving a guide does not change those identifiers.

​
Where an explanation comes from

The specification owns the language contract. The engine implements it. These docs explain it with links to the relevant public sources. How the documentation system works describes source revisions, publication checks and the distinction between a declared capability and an observed result. If a reference is missing, report the documentation gap with the object identifier, the page you came from and the relevant version.