> ## 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.
# Glossary
> Use plain-language definitions for the product and workflow terms that appear across Nitsor's public documentation.
Available now
## Glossary terms and common misreadings
The first five rows distinguish public availability from unresolved decisions and evidence. The remaining rows define the product and data vocabulary used across these docs.
| Term | Definition | Common misreading |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Available now | Behavior a visitor can use on the public site today and that automated tests verify. | It does not mean every Nitsor capability is available; the label applies only to the behavior carrying it. |
| Limited design-partner access | Pre-release work with a small number of teams. Scope, access, and suitability must be agreed directly. | It is not public access or a promise of acceptance, production access, or service levels. |
| Planned — not available yet | Intended behavior documented precisely enough to evaluate. Technical exports call this a target contract. | It is not a runnable capability. |
| Open | A decision that has not been settled. | It is not an additional availability level and does not mean evidence is merely unchecked. |
| Pending | Evidence that has not yet been provided or checked. | It is not an additional availability level and does not mean the decision itself is unsettled. |
| Adjudication | A final, accountable decision that resolves contested reviews or proposals and records a reason. | It is not an automatic average or an unrecorded tie-break. |
| Agent | Software that can choose and perform steps toward a goal. | An agent-readable file does not give an agent permission to act. |
| Annotation | A label or structured interpretation associated with source data. | It is not the source data itself. |
| Branch | In the target version model, an isolated line for proposed changes. | A branch name is not a permission. |
| Checkpoint | In the target version model, a recorded position in the event history that later commits derive from. | It is not itself a commit or an approval. |
| Commit | In the target version model, one attributable content change with a parent state. | It is not automatically approved. |
| Consensus | The result of an explicit rule applied to eligible review outcomes. | It is not the same as most completed tasks. |
| Content root | The identifier that fingerprints the content a commit covers, so identical content shares one root. It combines asset, instruction, label, project-metadata, review, taxonomy, and workflow roots. | It is not the commit identifier; the two are intentionally distinct. |
| Control plane | The part of a system that records identities, source references, versions, rules, and decisions. | It is separate from source-image storage, though it may need authorized reads and temporary processing. |
| Dataset state | The versioned source references, labels, taxonomy, declared transformations, and decision evidence needed to identify a candidate dataset. | It is more than a list of files or labels. |
| Design partner | A team working directly with Nitsor on a focused pre-release evaluation. | The term does not promise acceptance, production access, or service levels. |
| Gold check | In the intended review workflow, scoring submitted work against an item whose correct answer is already known. | Passing a gold check is not an approval or a release decision. |
| Industrial CT / NDT | Computed-tomography workflows used to inspect manufactured objects without destroying them. This is Nitsor's initial commercial focus. | It does not mean every volumetric workflow is industrial CT. |
| Landmark | A single marked point at a position in a volume, such as a tagged feature or defect location. | It is not a mask, box, or full segmentation. |
| Manifest | A structured list of the content and evidence belonging to a release. | No public Nitsor manifest format is available today. |
| MCP (Model Context Protocol) | A standard for connecting AI applications to tools and information sources. | No public Nitsor MCP server is available today. |
| Preflight | In the intended job model, a check that runs before a job starts and can refuse the job rather than let it run without its guarantee. | A refusal is a recorded outcome, not a crash. |
| Principal | A human or machine identity that can receive limited permissions and be named as the actor behind an action. | An identity is not permission without an explicit grant. |
| Provenance | Evidence showing where a change came from, including the relevant source, author, tool or model, earlier state, and decisions. | It is not just an author name or model label. |
| Release | In the target model, one approved dataset state with the evidence needed to explain and reconstruct it. | An export is not automatically a release. |
| Replay-tested | Verified by rebuilding state from the recorded event history and comparing the rebuilt result with the live one. | It is evidence about backend contracts, not about a public interface. |
| Review | An attributable assessment of a proposed change against a known instruction. | It is not itself an approval or final decision. |
| Runner | In the target model, a machine identity that can be assigned work and author proposals under its own name. | A runner cannot approve its own work. |
| Source reference | An identifier for source data held in another system. | A reference is not a copy or backup. |
| Surface | A general word for an interface a caller could reach, such as an API route, command, package, or webhook. | Naming a surface does not mean one is published. |
| Target contract | A precise description of intended behavior, written so a team can evaluate and test against it before the capability exists. | It is not proof that the described capability is available. |
| Taxonomy | The controlled set and meaning of labels used by a project. | It is not merely an uncontrolled list of label names. |
| Volumetric data | Data sampled across three spatial dimensions, such as industrial CT, medical CT, or MRI volumes. | It is not limited to medical imaging. |
| Voxel | One element of a three-dimensional volume, the volumetric equivalent of a pixel. | Voxel-level conflict handling is not an available capability. |
| Webhook | An automatic message one system sends to another over the web when a specified event occurs. | No public Nitsor webhook is available today. |
## Common mistakes and limits
* Terms describe the intended model; they do not prove an implementation.
* Similar words in another tool may carry different state or authority.
* Legal, medical, security, and standards definitions may require domain-specific review beyond this glossary.
## Next step
Return to the [Introduction](/) or search the documentation for the term you need in context.
Outcome
Understand a term without mistaking planned behavior for an available capability.