# Nitsor documentation

> Public documentation for Nitsor, a pre-release system of evidence for volumetric data, labels, reviews, and dataset releases. Every page states how much of what it describes you can use today.

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

## Docs

- [Introduction](https://docs.nitsor.com/index.md): Version control for 3D AI inspection data. Understand what Nitsor is, what a visitor can use today, and where each part of this documentation answers a different question.
- [Quickstart](https://docs.nitsor.com/quickstart.md): Take one useful first action today, using only the parts of Nitsor that a visitor can actually reach.
- [Product status](https://docs.nitsor.com/product-status.md): See what is available now, what is limited to design-partner work, and what is still planned.
- [Concepts](https://docs.nitsor.com/concepts/index.md): Learn the vocabulary Nitsor uses for dataset state, boundaries, roles, review decisions, and model proposals before reading any workflow.
- [Version model](https://docs.nitsor.com/concepts/version-model.md): Learn the intended relationship between projects, source references, dataset state, branches, commits, reviews, and releases.
- [Data boundary](https://docs.nitsor.com/concepts/data-boundary.md): Understand the intended separation between source volumes, version and decision records, temporary processing, and exports.
- [Roles and provenance](https://docs.nitsor.com/concepts/roles-provenance.md): Learn how identity, permissions, authorship, review, approval, and change history are intended to remain distinct.
- [Review, consensus, and adjudication](https://docs.nitsor.com/concepts/review-consensus-adjudication.md): Understand the intended decision model for independent reviews, agreement rules, conflicts, and accountable resolution.
- [Model-assisted prelabeling](https://docs.nitsor.com/concepts/model-assisted-prelabeling.md): Understand what guarantee a model proposal can carry, and why an under-calibrated job is refused before the model runs.
- [Guides](https://docs.nitsor.com/guides/index.md): Follow one job from beginning to end, from annotating a task to approving a dataset release or planning an integration.
- [Annotate and review](https://docs.nitsor.com/guides/annotate-and-review.md): Understand the intended annotation, review, and domain-expert experience without needing engineering knowledge.
- [Release a dataset](https://docs.nitsor.com/guides/dataset-release.md): Walk through the intended evidence and decisions for turning source references and reviewed labels into an approved dataset release.
- [Plan an integration](https://docs.nitsor.com/guides/plan-an-integration.md): Turn a proposed dependency on Nitsor into an acceptance test, using the evidence gate that applies to every interface listed as planned.
- [Design-partner onboarding](https://docs.nitsor.com/guides/design-partner-onboarding.md): Prepare a small, privacy-aware evaluation of Nitsor using one real volumetric-data workflow.
- [Reference](https://docs.nitsor.com/reference/index.md): Find the exact interfaces, contracts, deployment controls, and terms that exist today, each stated with its current boundary.
- [Integrations and public interfaces](https://docs.nitsor.com/reference/integrations.md): See which public interfaces exist today and which APIs, tools, and product integrations are still planned.
- [Public HTTP API](https://docs.nitsor.com/reference/api.md): Evaluate the implemented HTTP contract, its error vocabulary, and the hashed agent-credential authentication scheme.
- [Command-line interface](https://docs.nitsor.com/reference/cli.md): See the five implemented commands, their tested guarantees, and the distribution boundary that prevents public installation instructions.
- [Data model and contracts](https://docs.nitsor.com/reference/data-model.md): Understand the replay-proven event, authorization, version, workflow, and prelabel contracts without assuming an operator product exists.
- [Self-host mechanics](https://docs.nitsor.com/reference/self-host.md): Separate the tested mechanics of nitsor up from the complete self-hosted product that is not yet published.
- [Deployment and security](https://docs.nitsor.com/reference/deployment-and-security.md): Separate the public site's verified controls from planned product deployment, security, identity, compliance, and self-hosting capabilities.
- [Glossary](https://docs.nitsor.com/reference/glossary.md): Use plain-language definitions for the product and workflow terms that appear across Nitsor's public documentation.