version

A version in the distribution context is the semantic-version string that identifies a published snapshot of abcd — stamped into the curated release artifact at cut time and carried as the git tag of the single repo (adr-28), so the host can compare what is installed against what is available and users can update. The working tree stays unversioned; the version lives only in the cut artifact and its tag — the dev-unversioned / release-versioned polarity applied within one tree.

A version never sequences the work: the order of work is dependencies plus the lifecycle shelves (record families, adr-2609212115255771), and nothing is planned into a version. When abcd is PUBLISHED, a semantic version is the precise, correct term: launch ship derives it from the impact the shipped records declare (pre-1.0, a breaking change bumps the minor), and an all-internal or empty cut derives none.

When to use

Use "version" for the semver string of a published abcd snapshot — in the release artifact, the git tag, the marketplace entry, and the changelog.

When NOT to use

Do not use "version" for the sequencing of development work: that is dependencies and the shelves. A version is the output of publishing, never the unit that organises what ships together; the delivery grouping is a bundle.

Examples

• "launch ship stamps the release artifact 0.2.0 (strict SemVer, no leading v) and tags the repo v0.2.0."
• "Users update to the latest version with /plugin update abcd."

Related terms

• record families — the one page that maps the record families and how they relate
• phase: the retired sequencing unit; a version was never one
• release — the published act that carries a version