Skip to main content
Planned — not available yet 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

​
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 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 to define the smallest evaluation that could produce trustworthy evidence.
OutcomeCompare one of your own workflows against the intended Nitsor workflow and name the gaps.
AvailabilityPlanned — not available yet
AudienceAnnotators and reviewers, Technical program managers, ML, data, and software teams, Evaluators
PrerequisitesRead Product status; Know the concept vocabulary
Last verified2026-08-23