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

​
Choose your next step

Start a workflow

Install the engine, create a file and follow its first validation and run.

Look up a YAML field

Find its meaning, placement, type, related fields and pinned schema source.

Use a builtin tool

Browse tools, then open a dedicated reference such as nika:assert or nika:fetch.

Connect an application

Read the SDK contract, local and remote interfaces, and operational guides.

Understand the engine

Follow the layers, crate admission rules and architectural decisions.

Explore the Lab

Navigate an object, its source documents and its actual graph connections.

​
Find a specific reference

The Lab translates reviewed website documentation paths to these pages. For example, a former /language/stdlib/assert link opens 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; the Lab connects the captured sources and their identities. 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.