> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nika.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap

> What you can build with Nika today, the status of the 0.124 line, and where to follow the public work.

Nika lets you put AI workflows in an application, describe their permitted
effects, and inspect what happened after a run. This page separates what you
can use in 0.124 from the earlier plan the project keeps as a record.

## Start with what is available

| I want to… | Available path | Learn it |
| - | - | - |
| Add workflows to a TypeScript app | Published @supernovae-st/nika\@0.124.4; local execution with its bundled engine | [SDK quickstart](https://docs.nika.sh/sdk/start/quickstart.md) |
| Write and validate a workflow | Native CLI v0.124.4; canonical `.nika` files | [First workflow](https://docs.nika.sh/getting-started/first-workflow.md) |
| Choose what a workflow may do | Explicit permits and governed effects | [Security model](https://docs.nika.sh/concepts/security.md) |
| Inspect a run | Events, outputs, traces and receipts | [Traces](https://docs.nika.sh/concepts/traces.md) |
| Run against a resident server | The SDK's authenticated remote API, with a compatible server | [Remote client](https://docs.nika.sh/sdk/remote/client.md) |
| Turn a request into a workflow | The terminal Session (`nika`), or `nika compile`: exact skeletons offline, free intent with `--authoring-model` | [The terminal Session](https://docs.nika.sh/getting-started/session.md) · [Bounded authoring](https://docs.nika.sh/examples/bounded-authoring.md) |

> [!NOTE]
>
> The CLI and npm package have separate release channels. Read
> [Current status](https://docs.nika.sh/reference/status.md) for the exact documentation targets and
> [Releases](https://docs.nika.sh/changelog/releases.md) for published changes. Source on `main`, a
> closed issue, or an accepted design does not by itself mean a package shipped.
> [Known limits in 0.124](https://docs.nika.sh/changelog/known-limits.md) lists what the release does
> not do.

## What does “Compile” mean here?

Offline, with no model, `nika compile` writes exact skeletons
(`nika compile --list` names them), bounded support intents and conservative
edits of an existing file (`--base` with `--change`). An intent it cannot
settle stays incomplete and asks its questions; it never writes a substitute.

For a request in your own words, open the [terminal Session](https://docs.nika.sh/getting-started/session.md)
(`nika`) or run `nika compile "<request>" --authoring-model <provider/model>`.
A model you choose writes the candidate, and Nika checks it, and rehearses it
where it can, before anything is saved or run. Authoring with a large model can
take minutes, and a rehearsal skips model steps:
[Known limits in 0.124](https://docs.nika.sh/changelog/known-limits.md) lists what to expect.

Start with [the offline authoring path](https://docs.nika.sh/examples/bounded-authoring.md). The
[engine roadmap](https://github.com/supernovae-st/nika/blob/main/ROADMAP.md) and
[public engine issues](https://github.com/supernovae-st/nika/issues) track the
maintenance work.

## What happens after 0.124?

0.124 is the current release line. Work stays focused on maintenance,
security and the media capabilities workflows need; native video is planned
for 0.125. The 0.123.x line is the previous one. No 1.0 release is planned.
The engine roadmap and the specification keep the conditions once set for a
1.0 release as the record of that plan, not as a commitment:

* **Release and user experience qualification:** installation, documentation,
  editor setup and supported execution paths must work together.
* **The contract system:** everything that crosses a boundary carries a
  declared contract (types, errors, effects and bounds), and unknown
  information stays visible instead of being reported as success.
* **Long-term compatibility:** conformance, archives, deterministic checking,
  a compatibility promise and succession are launch conditions.
* **Design-partner release candidates:** the plan placed these before a
  launch.

Memory, retrieval and cognition were never a single launch condition: the
former Connectome umbrella, which required the whole memory subsystem before
1.0, was retired on 2026-10-08.

These were conditions, not delivery dates or claims of completion. The
[owning engine roadmap](https://github.com/supernovae-st/nika/blob/main/ROADMAP.md)
and the specification's
[timeline](https://github.com/supernovae-st/nika-spec/blob/main/timeline/timeline.yaml)
carry the detailed decisions. [Timeline and evidence](https://docs.nika.sh/reference/timeline.md)
explains how to read them without confusing a proposal with a shipped feature.

## Follow the work without losing the product story

| Question | Best source |
| - | - |
| What changed in a version? | [Published releases](https://docs.nika.sh/changelog/releases.md) |
| What does the current release not do? | [Known limits in 0.124](https://docs.nika.sh/changelog/known-limits.md) |
| What can I install now? | [Current status](https://docs.nika.sh/reference/status.md) |
| What work is still open? | [Engine issues](https://github.com/supernovae-st/nika/issues) and [SDK issues](https://github.com/supernovae-st/nika-client/issues) |
| Why is the architecture shaped this way? | [Layers](https://docs.nika.sh/architecture/layers.md) and [decisions](https://docs.nika.sh/architecture/adrs.md) |
| How did the project get here? | [Historical milestones](https://docs.nika.sh/changelog/history.md) |

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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.