Knowledge Portal · engineering documentation

Skip to content

ZAIXOS Engineering Platform — Version Transition Plan

Document type: Extraction Planning Specification
Version: 1.0 · Phase: 12-4
Status: Permanent execution authority


Purpose

Define the version lineage from ERP v1 embedded baseline through ZEP v1.0.0 GA to future platform versions — without semantic breaks at cutover.


Version transition timeline

ERP v1.0 (embedded)
    │  Semantic baseline: contracts@1, adapter 1.0.0-phase-11-9
    │  Product tag: v5.1-engineering-runtime-platform (historical)

Dual-run embedded + platform package (12-7–12-8)
    │  Platform package: 1.0.0-rc.* → 1.0.0

ZEP v1.0.0 GA (12-9)
    │  Tag: zaixos-platform@v1.0.0
    │  Consumer lock: platform 1.0.0, contractMajor 1

ZEP v1.x PATCH/MINOR
    │  Additive only; contracts@1 frozen

ZEP v2.0.0 (future)
    │  Requires contracts@2 ADR — out of extraction scope

Identity mapping

Historical identifierPlatform identifierNotes
ERP v1.0ZEP 1.0.0Same obligations
contracts@1 (implicit in ERP)contracts@1 explicit in lockFrozen
Cursor Adapter 1.0.0-phase-11-9cursor-adapter-v1 @ 1.0.0Renormalize semver at GA (content parity)
EOS v1.0 methodologyPlatform Core methodologySame files, new paths
Embedded docs/development/vendor/.../ + .zaixos/Host change only

Adapter version normalization

StageVersion string
Pre-extraction (Dental Clinic)1.0.0-phase-11-9
Platform repo during 12-61.0.0-rc.11.0.0-rc.n
GA (12-9)1.0.0

Rule: GA version bump is label only if workspace checksum unchanged vs rc final — documented in CHANGELOG.


Platform package versions during extraction

PhasePlatform versionTag type
12-5 ScaffoldNo tag
12-6 Extraction1.0.0-rc.1+Pre-release tags on platform repo
12-7 Consumer1.0.0-rc.finalConsumer pins rc until 12-8 pass
12-8 Validation1.0.0-rc.finalParity sign-off
12-9 GA1.0.0zaixos-platform@v1.0.0

Product (Dental Clinic) version independence

ArtifactVersioning
Product release tagsUnchanged — e.g. v4.x-* product phases
Platform pinplatform.lock @ 1.0.0 after 12-9
composer.lockTracks platform package

Product releases do not require platform MINOR bumps unless platform upgrade scheduled.


contractMajor transition rules

TransitionAllowed whenProcess
contractMajor: 1 → stays 1All platform 1.xDefault
contractMajor: 1 → 2Platform 2.0 ADRRe-cert adapters; migration guide
Product stays on 1Platform 2 releasedSupported 12 months PATCH on 1.x

Extraction phases: contractMajor MUST remain 1.


Embedded → vendored cutover

MilestoneEmbedded stateVendored state
Pre-12-7AuthoritativeAbsent
12-7 dual-runFrozen baselineActive dev
12-8Parity referencePrimary validation target
12-9Removed (stub only)Sole authority

Future platform versions (post-GA)

Per EVOLUTION_MODEL.md:

  • 1.x: Additive; Dental Clinic upgrades via lock bump + rematerialize
  • 2.x: MAJOR; Architect acceptance + migration guide mandatory

Extraction planning does not schedule v2.


Version documentation deliverables

DeliverablePhaseLocation
Platform CHANGELOG12-6+Platform repo root
Release compatibility matrix12-9docs/releases/v1.0.0.md
Consumer lock committed12-7.zaixos/platform.lock
Migration note ERP→ZEP12-7Product release doc + platform developer-guide § Migration

Version Transition Plan v1.0 — Phase 12-4.

ZAIXOS Knowledge Portal — public engineering docs at /docs · Staff operations at /admin