> ## Documentation Index
> Fetch the complete documentation index at: https://doc.blueapi.ir/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise Model: Versioning and Lineage Specification

> Enterprise Model versioning rules, semantic versioning, lineage to research candidates, compatibility guarantees, and deprecation policy.

EnterpriseModel defines the versioning, lineage, and compatibility rules for models promoted from research to production. This page specifies semantic versioning, the version chain structure, backward compatibility guarantees, and the deprecation policy that governs model retirement.

## Semantic Versioning

EnterpriseModel versions follow semantic versioning: `MAJOR.MINOR.PATCH`.

| Component | Change Type                                                 | Example          |
| --------- | ----------------------------------------------------------- | ---------------- |
| MAJOR     | Breaking change in architecture, tokenizer, or API contract | v1 to v2         |
| MINOR     | New capability, non-breaking architecture change            | v1.1 to v1.2     |
| PATCH     | Bug fix, quantization update, security patch                | v1.1.1 to v1.1.2 |

A major version increment requires full re-validation, security review, and acceptance testing. Minor and patch versions may reuse prior validation results if the change is contained and documented.

## Version Chain

The diagram below shows the lineage from research candidate to enterprise release.

```mermaid theme={null}
flowchart LR
    subgraph Research
        C1[Candidate A-7]
        C2[Candidate B-3]
        C3[Candidate C-12]
    end

    subgraph Enterprise
        V1[v1.0.0]
        V2[v1.1.0]
        V3[v2.0.0]
    end

    C1 -->|Promoted| V1
    C2 -->|Merged + Promoted| V2
    C3 -->|Promoted| V3

    V1 -->|Minor| V2
    V2 -->|Major| V3
```

Every enterprise version links back to one or more research candidates via [Model Lineage](/tracking/model-lineage). The lineage graph is immutable and auditable.

## Compatibility Guarantees

| Guarantee               | Scope                                                                                 | Duration                 |
| ----------------------- | ------------------------------------------------------------------------------------- | ------------------------ |
| Tokenizer compatibility | Same vocabulary, special tokens, and encoding within a major version                  | Until next major version |
| API contract            | Input schema, output schema, and error codes within a major version                   | Until next major version |
| Quantization parity     | FP16, BF16, INT8 outputs are deterministic given the same seed within a patch version | Until next patch version |

<Warning>
  Compatibility guarantees apply only to models served through the official [InferenceBackend](/deployment/inference). Custom backends or patched runtimes are not covered.
</Warning>

## Deprecation Policy

EnterpriseModel versions move through deprecation stages before archival.

| Stage       | Duration   | Behavior                                                                       |
| ----------- | ---------- | ------------------------------------------------------------------------------ |
| Active      | Indefinite | Full support, updates, and monitoring                                          |
| Deprecated  | 90 days    | No new features; security patches only                                         |
| End of Life | 30 days    | No patches; migration required                                                 |
| Archived    | Permanent  | Retained in [ArtifactStore](/tracking/artifact-registry) for audit; no serving |

Deprecation is announced via the model registry API and logged in [ExperimentTracker](/tracking/experiment-tracking). Clients subscribing to version events receive advance notice.

## State Transitions

An enterprise model progresses through the model lifecycle: DISCOVERED, IMPORTED, VALIDATED, REGISTERED, CANDIDATE, EVALUATED, PROMOTED, RELEASED, DEPLOYED, DEPRECATED, ARCHIVED. The transition from PROMOTED to RELEASED creates the enterprise version tag. See [Model Registry](/tracking/model-registry) for the full lifecycle specification.

## Integration

EnterpriseModel is managed by [DeploymentManager](/deployment/deployment-specification) during release and by [Model Update Protocol](/enterprise/model-update-protocol) during upgrades. Version metadata is stored in [ModelRegistry](/tracking/model-registry) and lineage is tracked in [Model Lineage](/tracking/model-lineage).