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

# Product status

> See what is available now, what is limited to design-partner work, and what is still planned.

<a className="nit-availability" data-availability="available-now" href="/product-status#status-definitions" aria-label="Available now. Read the status definitions."><span aria-hidden="true" className="nit-availability__dot" />Available now</a>

## Status definitions

**Available now** means a visitor can use the behavior on this public site today and automated tests verify it.

**Limited design-partner access** means the work is pre-release and shaped with a small number of teams. Scope, access, and suitability must be agreed directly. It is not a promise of production service.

**Planned — not available yet** means the documentation describes intended behavior so teams can evaluate it and give precise feedback. Technical exports call this a **target contract**. It is not a runnable product or integration.

**Open** marks a decision that has not been settled. **Pending** marks evidence that has not yet been provided or checked. Both describe unresolved decisions or evidence; they are not additional availability levels. Some tables also write **Not available** against interfaces where no public implementation of any kind exists; read it as a stricter restatement of Planned — not available yet, not as a fourth level.

The three availability labels are used the same way on every page of this documentation. This legend is the definition other pages rely on.

| Label                         | What it means                                                                                                | Evidence required                                                                                 | What it is not a claim of                                                                                      |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Available now                 | A visitor can use the behavior on this public site today.                                                    | Working behavior on the current public site, verified by automated tests.                         | Any capability outside this public site, and any promise about a future release.                               |
| Limited design-partner access | Pre-release work shaped with a small number of teams. Access, scope, and suitability are agreed directly.    | An implementation that an agreed design partner can exercise within the agreed pre-release scope. | A public release, a production service, a service level, or an offer to accept any particular team.            |
| Planned — not available yet   | The documentation describes intended behavior so teams can evaluate the direction and give precise feedback. | A written description only. Technical exports call this a target contract.                        | A runnable product, screen, command, public interface, or integration, even where the text uses present tense. |

### The four readiness states used on the marketing pages

The home page carries one readiness band with four states, and it links here because this page defines them. They are a different vocabulary from the three availability labels above, on purpose, and neither one is a translation of the other. The availability label answers **who can reach a capability**. The readiness state answers **how far the work has got**. A capability can be built and reachable by nobody, which is why both exist.

| State           | What it means                                                                          |
| --------------- | -------------------------------------------------------------------------------------- |
| Live today      | You can use it right now, on this site.                                                |
| In build for v0 | Committed for the first release. The code exists. You cannot use it yet.               |
| After v0        | Named and sequenced, not started. A design partner needing it is what starts the work. |
| Still open      | A decision nobody has made yet. It is here so you can ask about it.                    |

The summary table in the next section abbreviates these to **Live**, **In build**, **After v0** and **Open** to fit a narrow column. The four full names above are the definitions.

**Where the two vocabularies disagree about the same capability, the availability level in the capability status matrix is correct.** That matrix is checked row by row against the code and carries a depth note for each one. A readiness state is a one-word summary and cannot carry a boundary.

## Available now

* Public marketing, planned-pricing, FAQ, contact, and draft legal pages.
* Public documentation at `docs.nitsor.com`.
* A contact form with input validation and safe email formatting covered by automated tests. Those tests do not prove live email delivery.

## Limited design-partner access

Nitsor is looking for teams with recurring industrial CT, medical CT, or MRI workflows who control their source storage and can evaluate the product with real constraints. Participation, scope, support, and production suitability must be agreed directly; this page does not promise acceptance or a service level.

The implemented [Public HTTP API](/reference/api), [command-line interface](/reference/cli), and replay-tested [data model and contracts](/reference/data-model) are available only inside an agreed design-partner environment. Their reference pages state the distribution and product-readiness limits that still apply.

Format depth is also narrow. Reference registration and browser rendering of supported uncompressed Part 10 slices exist; public-corpus, live-storage, and production evidence remain pending. VGI/VOL has a viewable registration path. MRD and TIFF/xtekct register as raw. NSI, REK, FLT, CB, and SBM register with explicit unsupported states. DICONDE, MetaImage, and NRRD remain planned.

## Planned — not available yet

The following areas are described so teams can review the direction, but they are not available as a released product:

* complete project, branch, commit, review, agreement, final-decision, and release workflows;
* source-data registration and data-location guarantees in a deployed product;
* public SDK, Model Context Protocol (MCP), webhook, or agent integrations;
* a supported self-hosted product, release pipeline, upgrade path, or rollback path;
* enterprise identity, authorization, billing, compliance, or hosted inference.

The tested [`nitsor up` mechanics](/reference/self-host) start an incomplete dependency stack, not a supported Nitsor product. If you encounter a planned workflow example, read it only as a target contract rather than as proof of an available product.

## Readiness at a glance

Twelve lines, in the four-state vocabulary the home page band uses. This is the readable summary. The capability status matrix below it is the register, and it governs.

| Capability                                            | State    | What exists today                                                                            |
| ----------------------------------------------------- | -------- | -------------------------------------------------------------------------------------------- |
| This website and the public documentation             | Live     | Including the contact form, which reports a clear error if delivery fails.                   |
| Full-depth 3D viewer and editor                       | In build | Every editor screenshot on this site is a design mockup, labelled as one.                    |
| Version graph, branch, semantic diff, three-way merge | In build | The spine. Nothing above it is meaningful without it.                                        |
| Dataset releases and frozen manifests                 | In build | Rebuilding a dataset outside Nitsor is the target. We have not demonstrated it.              |
| Routing, review, consensus, adjudication, gold tasks  | In build | SAM 2.1 proposals and risk-controlling routing are the whole committed model scope.          |
| API, CLI, SDK, single-node self-host                  | In build | The specification defines these contracts. Nothing answers a request yet.                    |
| Calibration, Certificates, auto-accept                | In build | Enterprise tier. We have designed the independent verifier. Nobody has written it.           |
| DICOMweb, PACS and VNA adapters                       | After v0 | For v0 you bring industrial MRI and DICOM in through your own object storage.                |
| General agents and MCP                                | After v0 | v0 distinguishes humans, services and model executions. General agent principals come later. |
| Which licence in the FSL/BSL family                   | Open     | We also cannot publish before IP clearance, and that has not happened.                       |
| Published packages and prices                         | Open     | Seatless is settled. The numbers are not.                                                    |
| Exact supported format list per release               | Open     | Round-trip tests decide this, not a marketing checklist.                                     |

### Where this summary is rougher than the matrix

Six of the twelve rows above compress a boundary that the matrix states exactly. Read the matrix for any of them before you rely on it.

* **Full-depth 3D viewer and editor** reads as unreachable. It is not: the limited editor renders supported registered data for an agreed design partner. What no one can use is the full-depth viewer.
* **API, CLI, SDK, single-node self-host** is four things in one row and they are not at the same stage. The HTTP API and the command-line interface are built and reachable inside an agreed design-partner environment, so "Nothing answers a request yet" is wrong for those two. No SDK package exists, and the self-host installer starts an incomplete dependency stack rather than a Nitsor product.
* **Version graph, branch, semantic diff, three-way merge**, **Dataset releases and frozen manifests**, and **Routing, review, consensus, adjudication, gold tasks** read as "the code exists". For these three the matrix is stricter: an early backend description exists, there is no user interface, and no release can be created or approved.
* **Calibration, Certificates, auto-accept** says it plainly in its own note and the matrix agrees. Nobody has written it.

Two capabilities have no row in the summary at all and do have one in the matrix: **hosted workspace and sign-in**, and **hosted operation**. Both are marked Pending, meaning no deployed-operation evidence has been reviewed, so no reachable hosted service is claimed.

## Capability status matrix

This is the canonical list of availability levels for Nitsor capabilities. Other pages link here rather than repeating it, so if a statement elsewhere disagrees with this table, this table is correct.

Each row carries an availability label or an explicit pending-evidence marker, checked on 18 August 2026. Only the last row is **Available now**. The Depth column says how far the work has progressed in plain words. A capability that exists only as a backend record has no screen, command, or public interface a customer can use.

| Capability                                             | Status                        | Depth today                                                                                                                  |
| ------------------------------------------------------ | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Hosted workspace and sign-in                           | Pending                       | Built; no deployed-operation evidence was reviewed, so no reachable hosted workspace is claimed.                             |
| Account roles and permissions                          | Limited design-partner access | Built.                                                                                                                       |
| Recorded authorization decisions and attribution       | Limited design-partner access | Built as backend records. No screen presents them.                                                                           |
| Project record and event history                       | Limited design-partner access | Built as backend records. No screen presents them.                                                                           |
| Version model (branches, commits, merges)              | Planned — not available yet   | An early backend description exists. There is no user interface.                                                             |
| Review, consensus, and adjudication workflow           | Limited design-partner access | A reviewer can accept, correct, or reject a held review task in the editor. Consensus and adjudication have no interface.    |
| Model-assisted prelabeling with calibrated uncertainty | Planned — not available yet   | A description exists, including how the system declines a case it cannot support. No model runs.                             |
| Medical-image (DICOM) series registration              | Limited design-partner access | Supported uncompressed Part 10 slices can register and render in the browser within the limited editor.                      |
| Volumetric viewer                                      | Limited design-partner access | The limited editor renders supported registered data; the standalone demo still uses synthetic data.                         |
| Public HTTP API                                        | Limited design-partner access | Built, with hashed scoped agent-credential authentication. See [Public HTTP API](/reference/api).                            |
| Command-line interface                                 | Limited design-partner access | Five command families are built.                                                                                             |
| TypeScript and Python SDKs                             | Planned — not available yet   | No package exists.                                                                                                           |
| Dataset releases with signed manifests                 | Planned — not available yet   | Described only. No release can be created or approved.                                                                       |
| Self-host installer                                    | Planned — not available yet   | The installer mechanics are tested, but no complete application package exists to install.                                   |
| Hosted operation                                       | Pending                       | No deployed-operation evidence was reviewed; no running hosted service is claimed.                                           |
| Industrial (non-DICOM) file formats                    | Limited design-partner access | VGI/VOL is viewable; MRD and TIFF/xtekct are raw; five named families register as unsupported; other formats remain planned. |
| Analytics and progress reporting                       | Planned — not available yet   | Described only.                                                                                                              |
| Documentation and agent-readable exports               | Available now                 | Published on this site and verified by automated tests.                                                                      |

## What counts as evidence

For these docs, “available” is limited to behavior a visitor can use on the current public site and that automated tests verify. A future release may add product capabilities. A roadmap statement or a sentence written in the present tense is not enough to call something available.

| Counts as evidence                                          | Does not count as evidence                           |
| ----------------------------------------------------------- | ---------------------------------------------------- |
| Working behavior on the current public site.                | A roadmap statement or planned date.                 |
| An automated test that verifies the named behavior.         | A sentence written in the present tense.             |
| A recorded result tied to a specific version.               | A demonstration that cannot be repeated.             |
| A limitation stated together with the capability it limits. | A capability described without its current boundary. |

<section aria-labelledby="docs-rich-synthetic-review-distribution" aria-describedby="docs-rich-synthetic-review-distribution-caption" className="nit-fig" role="figure">
  <div className="nit-fig__header">
    <p className="nit-fig__status">Synthetic review</p>
    <h2 className="nit-fig__title" id="docs-rich-synthetic-review-distribution">What the synthetic review measured</h2>
  </div>

  <div className="nit-fig__body">
    A frozen snapshot is a saved copy reviewed without later edits. These scores apply only to the first two frozen documentation snapshots. The current published documentation was not rescored. **Pending:** repeat this synthetic review with the current public documentation.

    This is documentation-clarity evidence only, not customer, product, domain, legal, security, or production validation.

    <svg aria-labelledby="review-distribution-title review-distribution-description" className="nit-fig__graphic nit-fig__graphic--lg" role="img" viewBox="0 0 640 220"><title id="review-distribution-title">Synthetic documentation review scores</title><desc id="review-distribution-description">Of 15 synthetic persona reviews, 5 scored 9 out of 10 and 10 scored 10 out of 10.</desc><line className="nit-fig__rule" strokeWidth="2" x1="160" x2="600" y1="178" y2="178" /><g><line className="nit-fig__rule" strokeWidth="1" x1="160" x2="160" y1="42" y2="184" /><text className="nit-fig__tick" textAnchor="middle" x="160" y="204">0</text></g><g><line className="nit-fig__rule" strokeWidth="1" x1="380" x2="380" y1="42" y2="184" /><text className="nit-fig__tick" textAnchor="middle" x="380" y="204">5</text></g><g><line className="nit-fig__rule" strokeWidth="1" x1="600" x2="600" y1="42" y2="184" /><text className="nit-fig__tick" textAnchor="middle" x="600" y="204">10</text></g><g><text className="nit-fig__label" x="18" y="84">9/10</text><rect className="nit-fig__bar--outline" height="42" strokeDasharray="7 5" strokeWidth="2" width="220" x="160" y="54" /><text className="nit-fig__label nit-fig__label--sm" textAnchor="start" x="392" y="81">5 personas</text></g><g><text className="nit-fig__label" x="18" y="146">10/10</text><rect className="nit-fig__bar" height="42" strokeWidth="2" width="440" x="160" y="116" /><text className="nit-fig__label nit-fig__label--sm" textAnchor="end" x="588" y="143">10 personas</text></g></svg>

    | Score         | Personas |
    | ------------- | -------- |
    | 9/10          | 5        |
    | 10/10         | 10       |
    | Total reviews | 15       |
  </div>

  <p className="nit-fig__caption" id="docs-rich-synthetic-review-distribution-caption">This is documentation-clarity evidence only, not customer, product, domain, legal, security, or production validation.</p>
</section>

## Next step

Return to the [Introduction](/) or [contact the team](https://nitsor.com/contact) with the workflow you want to evaluate and the evidence you would need before adopting it.

<table className="nit-page-details" aria-label="Page details">
  <tbody>
    <tr><th scope="row">Outcome</th><td>Cite the correct availability level when discussing a Nitsor capability.</td></tr>
    <tr><th scope="row">Availability</th><td>Available now</td></tr>
    <tr><th scope="row">Audience</th><td>Evaluators, Technical teams, Operational leaders, AI agents</td></tr>
    <tr><th scope="row">Prerequisites</th><td>Read the Introduction</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-08-18</td></tr>
  </tbody>
</table>