Trace a volumetric dataset from source to release.
Nitsor is being designed to connect source scans or files, labels, definitions, reviews, and release decisions in a single history that shows who or what did each step.
Planned, not available. There is no released product workflow, public software, or deployment option today.
- Human
- Model
- Service
- Record
The website is available. The product workflow is not.
The public site is available. The product workflow is not. “Open” marks an unsettled decision. “Pending” marks evidence that has not been supplied or checked.
- Available on this site
- Public pages, documentation, and a contact form are available. The form reports a clear error if delivery fails.
- Planned: not available
- The version, review, decision, release, storage, integration, identity, and deployment workflows described here.
- Open
- These decisions remain unsettled: exact supported formats, fields, retention, how a release is marked as authentic, export behavior, deployment model, and software licence.
- Pending
- A live email-provider delivery receipt for the contact form has not been collected.
A release should answer four ordinary questions.
A release may depend on source data, label state, model outputs, definitions, and approvals held in different systems. The planned record is meant to connect those facts without treating a proposal as an approval.
| Question | Planned record | Status today |
|---|---|---|
| Which source scans or files are included? | Stable references and a check that the files are unchanged | Planned: no public registration workflow |
| Which labels, definitions, and transformations changed? | A history of changes linked to the previous version | Planned: no public version workflow |
| Who or what proposed, reviewed, and decided? | Separate proposal, review, and decision records | Open: permissions and identity rules remain unsettled |
| Can the accepted release be reconstructed? | A release record that can be checked outside the system that created it | Planned: no public reconstruction workflow |
Which source scans or files are included?
- Planned record
- Stable references and a check that the files are unchanged
- Status today
- Planned: no public registration workflow
Which labels, definitions, and transformations changed?
- Planned record
- A history of changes linked to the previous version
- Status today
- Planned: no public version workflow
Who or what proposed, reviewed, and decided?
- Planned record
- Separate proposal, review, and decision records
- Status today
- Open: permissions and identity rules remain unsettled
Can the accepted release be reconstructed?
- Planned record
- A release record that can be checked outside the system that created it
- Status today
- Planned: no public reconstruction workflow
Keep proposals, reviews, and decisions separate.
This sequence explains the planned model. It is not a product walkthrough. Each stage keeps a different record so a proposal cannot be mistaken for approval.
- 01
Reference
Identify source scans or files and the context needed to interpret them. A reference points to a file; it does not copy it.
- 02
Propose
Keep a focused human or machine proposal separate from accepted dataset history.
- 03
Record
Record what changed, the previous version, who or what created it, and the relevant model or tool version.
- 04
Review
Keep assessments distinct from the authorized decision that accepts, returns, or rejects work.
- 05
Release
Name one accepted dataset state and the evidence required to explain it. Reconstruction remains unproved.
Planned No public interface can execute, review, approve, or release this sequence today.
In the planned design, source volumes stay in storage you control.
This does not mean the product would never read or create data. Viewing, checking, converting, or running a model may require authorized reads and temporary or derived files. A released implementation must explain what it reads, creates, keeps, and deletes.
Planned data boundary
Keep source volumes in customer-controlled storage.
The intended product would store references to source volumes and the records needed to explain work. It may create temporary copies or derived files for viewing, validation, conversion, model runs, or export. Where those files live, how long they remain, and how deletion and export work are still open.
Start with one decision from your current work.
We are looking for teams with recurring industrial CT or non-destructive testing work who control their source storage and can describe how labels are proposed, reviewed, and accepted. Start with a privacy-safe workflow description. Never send credentials, patient data, customer data, scans, or storage locations.
Contact does not promise acceptance, delivery, a service level, or production support.