> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/releases/inspect-download-and-validate.md).

# Inspect, download, and validate

Prove release integrity in the downstream consumer.

Unitlab processing success confirms the release was created; downstream validation confirms the release is useful. Both are required for acceptance.

### Before you make the change

* Know the expected item count, schema, geometry conventions, group behavior, splits, and source path model.
* Use the same parser or consumer that production will use.
* Define acceptance tolerances and the owner of a failed validation.

![Release overview and data inspection](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FeMSyrUXzrEfCeiYryFcW%2Frelease-detail.png?alt=media\&token=9a228bde-4a68-4e78-bf9d-ec843ad3415f)

*Inspect release metadata and sample content before download, then reproduce the same checks in the actual downstream environment.*

### Understand the product behavior

Data Space contains **My Releases** and **Public Releases**, toggled from the page header. A release detail contains Overview, Data, and, on private workspace releases, Settings.

Opening a release item uses a read-only annotation viewer appropriate to its data family. It reuses the familiar modality surface but disables mutation. This lets teams inspect exactly what a release contains without accidentally changing the project history that produced it.

Making a release public requires license selection. Release deletion is permission- and subscription-gated. If the latest release version is deleted, the previous version becomes latest.

### Export formats

Use the current [export format matrix](/documentation/releases/export-formats-and-source-inclusion.md) to select the format for each data family. Check that it preserves the geometry, properties, temporal state, and source context your consumer requires.

For [LiDAR Annotation](/documentation/annotations/lidar-annotation.md), use UUEF and validate the scene manifest, calibration, point-label arrays, and geometric tracks together. Test a small release with the downstream parser before exporting the full dataset.

### SDK export behavior

The SDK can:

* create a release from a project;
* specify `export_type="UUEF"`;
* define split ratios such as 80% train and 20% test;
* list and retrieve releases;
* download annotations for a selected split;
* download associated files to a destination folder.

The SDK supports UUEF creation and split-aware annotation and file downloads. See [Export formats and source inclusion](/documentation/releases/export-formats-and-source-inclusion.md) for the current matrix and family-specific restrictions.

### Accept the downstream handoff

{% stepper %}
{% step %}

#### 1. Inspect in Unitlab

Review status, counts, version, project, sources, splits, format, settings, and representative items.
{% endstep %}

{% step %}

#### 2. Download deliberately

Use the approved destination and source-handling method.
{% endstep %}

{% step %}

#### 3. Parse the output

Load annotations, properties, relations, temporal data, groups, and source references with the production parser.
{% endstep %}

{% step %}

#### 4. Check semantics and geometry

Compare representative output to the Workbench and ontology version.
{% endstep %}

{% step %}

#### 5. Reconcile counts and splits

Confirm every expected item and no unintended item is present.
{% endstep %}

{% step %}

#### 6. Record acceptance

Store release ID, version, source dataset versions, ontology, workflow, model versions, format, split policy, exclusions, and validation result.
{% endstep %}
{% endstepper %}

### Decisions that affect production

| Decision   | Production guidance                                                                                                                            |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Mismatch   | Stop consumption, isolate the scope, and determine whether the cause is source, project state, format mapping, processing, or parser behavior. |
| Correction | Create a new controlled release rather than altering a delivered artifact silently.                                                            |
| Retention  | Retain enough metadata and artifacts to reproduce the handoff under the organization policy.                                                   |
| Consumer   | Acceptance belongs to the real downstream owner.                                                                                               |

### Continue the operating flow

* Promote the accepted release to its intended training or analysis pipeline.
* Create a new version for any correction.
* Use the release record during audit or model-reproduction work.

***

> **Continue with Unitlab:** [training-data curation workflows](https://unitlab.ai/en/data-curation)