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

> ## Agent Instructions
> Nitsor is a pre-release product. Every page in this documentation carries an availability status in its frontmatter (`availability`) and, as the first element of its body, a link labelled `Available now`, `Limited design-partner access`, or `Planned - not available yet`. That label is binding: it says whether a reader can use the behaviour the page describes.
> A page written in the present tense is not a claim that the behaviour ships. Where the availability label says `Planned - not available yet`, the page describes a target contract and there is no runnable product, screen, command, or public interface behind it.
> Every readiness claim this documentation makes lives on the Product status page. If any statement elsewhere disagrees with the capability status matrix on that page, the matrix is correct.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# Guides

> Follow one job from beginning to end, from annotating a task to approving a dataset release or planning an integration.

<a className="nit-availability" data-availability="target-contract" href="/product-status#status-definitions" aria-label="Planned — not available yet. Read the status definitions."><span aria-hidden="true" className="nit-availability__dot" />Planned — not available yet</a>

Each guide walks one job from its first step to the evidence it leaves behind. Read them as a description of the workflow Nitsor is meant to support, not as instructions you can follow in a product today.

**Status: mostly a target contract.** Three of the four guides describe behavior that is not available as a released product. Only the limited annotation editor described in the first guide exists, and only inside an agreed design-partner workspace.

## The four guides

| Guide                                                          | The job it covers                                                                           | Availability                  |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------- |
| [Annotate and review](/guides/annotate-and-review)             | Open assigned work, label it, submit it, and see it reviewed, returned, or escalated.       | Limited design-partner access |
| [Release a dataset](/guides/dataset-release)                   | Turn a candidate source set and reviewed labels into one approved, reconstructable release. | Planned — not available yet   |
| [Plan an integration](/guides/plan-an-integration)             | Decide what evidence an interface must produce before you depend on it.                     | Planned — not available yet   |
| [Design-partner onboarding](/guides/design-partner-onboarding) | Prepare a small, privacy-aware evaluation using one real workflow.                          | Limited design-partner access |

## How to read a guide

Every guide separates what a person does from what the system records, because the record is what makes the work reviewable later. Where a step has no implementation, the guide says so in the step rather than in a footnote.

Use a guide as a worksheet against your own process. The steps you cannot answer for your current workflow are the evidence gaps worth discussing, whether or not you ever adopt Nitsor.

## Common mistake

Do not treat a complete guide as proof that the product path exists. A finished description is a target contract; the [capability status matrix](/product-status#capability-status-matrix) is the register that says what is built.

## Next step

Start with the guide closest to the work you already do, then use [Design-partner onboarding](/guides/design-partner-onboarding) to define the smallest evaluation that could produce trustworthy evidence.

<table className="nit-page-details" aria-label="Page details">
  <tbody>
    <tr><th scope="row">Outcome</th><td>Compare one of your own workflows against the intended Nitsor workflow and name the gaps.</td></tr>
    <tr><th scope="row">Availability</th><td>Planned — not available yet</td></tr>
    <tr><th scope="row">Audience</th><td>Annotators and reviewers, Technical program managers, ML, data, and software teams, Evaluators</td></tr>
    <tr><th scope="row">Prerequisites</th><td>Read Product status; Know the concept vocabulary</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-08-23</td></tr>
  </tbody>
</table>