> ## 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.

# Find your documentation

> Choose a guide, look up a language field or tool, and follow the source behind an explanation.

`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

<CardGroup cols={2}>
  <Card title="Start a workflow" icon="play" href="/getting-started/first-workflow">
    Install the engine, create a file and follow its first validation and run.
  </Card>

  <Card title="Look up a YAML field" icon="code" href="/reference/language/overview">
    Find its meaning, placement, type, related fields and pinned schema source.
  </Card>

  <Card title="Use a builtin tool" icon="wrench" href="/reference/builtins">
    Browse tools, then open a dedicated reference such as nika:assert or nika:fetch.
  </Card>

  <Card title="Connect an application" icon="plug" href="/sdk/overview">
    Read the SDK contract, local and remote interfaces, and operational guides.
  </Card>

  <Card title="Understand the engine" icon="layer-group" href="/concepts/architecture">
    Follow the layers, crate admission rules and architectural decisions.
  </Card>

  <Card title="Explore the Lab" icon="diagram-project" href="/guides/explore-lab">
    Navigate an object, its source documents and its actual graph connections.
  </Card>
</CardGroup>

## Find a specific reference

| You are looking for                              | Open                                                                            |
| ------------------------------------------------ | ------------------------------------------------------------------------------- |
| A word such as `after`, `jitter` or `additional` | [Language field index](/reference/language/overview)                            |
| A tool's arguments and failure behavior          | [Builtin index](/reference/builtins), then its dedicated page                   |
| A complete workflow to adapt                     | [Examples](/examples/overview) and [templates](/guides/templates)               |
| An error or refused permission                   | [Diagnostics](/reference/error-codes) and [security](/concepts/security)        |
| A model or provider                              | [Provider reference](/reference/providers-catalog)                              |
| A crate or layer                                 | [Layer registry](/architecture/layers) and [admission](/architecture/admission) |
| What is actually released                        | [Current engine status](/reference/status)                                      |
| A future capability                              | [Roadmap](/changelog/roadmap), read separately from released status             |
| Documentation for an agent                       | [Documentation index](https://docs.nika.sh/llms.txt)                            |

## Arriving from an older link

The Lab translates reviewed website documentation paths to these pages. For
example, a former `/language/stdlib/assert` link opens
[the assert reference](/reference/tools/assert); `/templates` opens
[the template guide](/guides/templates). 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](/reference/knowledge-system) 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](https://github.com/supernovae-st/nika-docs/issues)
with the object identifier, the page you came from and the relevant version.