Skip to main content
Planned — not available yet These five pages define the words the rest of the documentation depends on. Read them before a guide or a reference page, because a guide that uses those words loosely is a guide you cannot check. Status: mostly a target contract. Four of the five concept pages describe intended behavior that is not available as a released product. The exception is the data boundary, where a limited design-partner implementation exists. Each page states its own boundary in its first paragraph.

​
The five concepts

​
How the concepts fit together

A project holds one related history. Within it, a dataset state names the source references, labels, taxonomy, and declared transformations that belong together. A branch isolates a proposal; a commit records one attributable content change; a review assesses that change; consensus and adjudication decide what happens to it; and a release names one approved dataset state together with the evidence needed to reconstruct it. Two ideas cut across all of that. The data boundary says what Nitsor holds and what stays in your storage. Provenance says where each change came from, who or what made it, and which earlier version it changed.

​
Common mistake

Do not read these definitions as a description of software you can open. They are a target contract: a precise statement of intended behavior, written so a team can test it before the capability exists. No screen, command, or public interface implements the complete model today.

​
Next step

Read Version model first, then pick the guide closest to the work you already do.
OutcomeUse the same words the rest of this documentation uses, and know which of them describe planned behavior.
AvailabilityPlanned — not available yet
AudienceTechnical program managers, ML and data teams, Reviewers and domain experts, Researchers
PrerequisitesRead Product status
Last verified2026-08-23