> 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/release-notes/enterprise-documentation-revision.md).

# Enterprise documentation revision

{% hint style="info" %}
**Published:** July 29, 2026 · **Scope:** Home, Documentation, API/SDK/CLI, Solutions, and Release Notes · **Audience:** all Unitlab users, evaluators, operators, administrators, developers, and downstream data teams
{% endhint %}

### Summary

The Unitlab developer site now documents the current July 2026 platform and SDK as an enterprise operating manual. Product content is grounded in the current platform overview, current product behavior, current demos, and the Unitlab SDK 3.0.0 codebase. Legacy documentation content is not used as a product source.

### Information architecture

Documentation and Solutions use a compact section → page hierarchy, matching the preferred Solutions navigation model. Each section expands to reveal its task or blueprint pages, while the API/SDK/CLI reference remains a flat command-and-resource index. Titles begin with the user task or operating decision rather than an internal feature inventory.

Documentation covers the platform object model, production quickstart, ingestion and cloud data, Data Space, curation, Data Groups, embeddings, datasets and versions, projects, the shared Workbench, Multiview, image, video, audio, text, document, medical, AI-assisted annotation, ontologies, workflows, queues, quality operations, administration, AI model management, releases, automation, operating patterns, capability mapping, and terminology.

### Procedural page standard

Core product guides identify the intended audience and completion outcome, list prerequisites, show an end-to-end flow, provide an ordered procedure, explain current control behavior, define verification checks, document failure recovery, and state the operational evidence to retain.

The video-annotation guide now covers setup, playback and frame navigation, geometry, temporal ranges, full and directional Auto-Tracking, multi-object tracking, interpolation, dynamic object properties, dynamic Item Properties, timeline behavior, mask interpolation, drift and scene-cut review, validation, and workflow submission.

### Developer reference standard

The API/SDK/CLI reference covers 45 current SDK 3.0.0 tasks. Each page includes prerequisites, an operational sequence, the relevant public interface and example, read-after-write verification, authentication and permission handling, timeout and partial-failure recovery, and production safeguards.

### Solution blueprint standard

Solutions covers industry use cases, multimodal patterns, human–AI operations, quality governance, model-in-the-loop iteration, architecture, rollout, and planning. Every blueprint begins with the decision contract, preserves required context, connects ontology and workflow design, and ends with validation gates, risk controls, and production evidence.

### Operator action

* [ ] Update internal bookmarks from former nested routes to the visible flat routes.
* [ ] Use the Documentation production quickstart for a representative pilot.
* [ ] Train annotators and reviewers with the Workbench and modality-specific guides.
* [ ] Use API/SDK/CLI pages that match the pinned Unitlab 3.0.0 environment.
* [ ] Use a Solution blueprint to record context, policy, workflow, quality, and release decisions.
* [ ] Report factual or procedural gaps with the exact page, current product state, expected behavior, and affected role.

### Verification

The public site was checked after publication for grouped Documentation and Solutions sidebars, expand controls, nested routes, section-aware breadcrumbs, rendered Mermaid flows, callouts, step sequences, tables, checklists, code blocks, and repaired Home links.

### Known visual-asset boundary

Current product screenshots should be published only through the GitBook file library or another approved first-party asset path. The available GitBook connector can read the space file library but does not expose a native binary-upload operation in this environment. The documentation therefore uses current-source diagrams, structured tables, and interface-specific text where an approved uploaded product image is not available; it does not substitute legacy marketing images.