Skip to main content
Nika lets you put AI workflows in an application, describe their permitted effects, and inspect what happened after a run. This page separates the parts you can use from the goals that still require implementation and evidence.

​
Start with what is available

The CLI and npm package have separate release channels. Read Current status for the exact documentation targets and Releases for published changes. Source on main, a closed issue, or an accepted design does not by itself mean a package shipped.

​
What does “Compile” mean here?

The released command creates a workflow from a bounded skeleton. It is a useful starting point you can check, edit and run. Broader natural-language composition, cross-surface SDK integration and advanced compiler goals need their own release and qualification evidence. The name alone does not establish those capabilities. Start with the available authoring path; follow the engine roadmap and public engine issues for ongoing work.

​
What must be ready before the official launch?

The public roadmap targets semantic versioning toward 1.0. The native engine is already available, but that availability is separate from completing the original launch requirements. The owning roadmap and specification describe:
  • Release and user experience qualification: installation, documentation, editor setup and supported execution paths must work together.
  • The contract system and whole Connectome: the planned memory and cognition system must meet its declared scope and evidence requirements.
  • Long-term compatibility: conformance, archives, deterministic checking, a compatibility promise and succession are launch conditions.
  • Design-partner release candidates: the public roadmap places these before the official launch.
These are conditions, not delivery dates or claims of completion. The owning engine roadmap and the specification’s timeline carry the detailed decisions. Timeline and evidence explains how to read them without confusing a proposal with a shipped feature.

​
Follow the work without losing the product story

If you are evaluating Nika, begin with one small workflow in your application. Use its output and trace to judge the available product; use the roadmap to understand its direction.