← Back to catalogue
Research draft

Model registration, versioning and acceptance

EM-XCT-10 · em-xct-10

Support accountable acceptance and traceable use of model releases through explicit release identity, reproducibility evidence and recorded publication decisions.

Enterprise profiles Enterprise contract EnterpriseXCT

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Bundle → Layer → Finding → Questions Filled

3 bundles · 4 layers · 4 findings · 11 questions

Registration This bundle describes a release manifest and the basis for interpreting its registration claims.

Manifest

This layer records the declared identity, dependencies and semantic fingerprint of a release.

Registration completeness

This finding assesses whether one manifest contains supported and sufficiently identified registration declarations.

  1. What role, schema, semantic version and dependencies does this manifest declare?
  2. Does this manifest record a computed semantic fingerprint or a placeholder?
  3. What versioned computation, semantic inputs and equivalence rules does this fingerprint specification declare?
  4. What document title and version, publication date or immutable revision does this supporting source reference identify?
Release and references This bundle describes release references and recorded restrictions on publication or continued use.

Release

This layer describes the immutability of references recorded for one release.

Immutable reference

This finding assesses whether a release reference identifies an immutable target.

  1. What immutable version or content digest does this release reference record?
  2. Does this dependency record specify a wildcard, moving branch or other mutable reference?

Holds and withdrawal

This layer describes recorded publication holds and the audit consequences of withdrawal.

Publication hold

This finding describes restrictions on release acceptance and retained evidence after withdrawal.

  1. What open publication holds and responsible roles does this release record identify?
  2. What evidence does this withdrawal record reference for reproducing the withdrawn release for audit?
Acceptance This bundle describes evidence and decisions supporting release acceptance.

Conformance evidence

This layer distinguishes installation evidence, conformance evidence and acceptance authority.

Assurance evidence

This finding assesses the recorded basis and limits of a release acceptance claim.

  1. What separate installation and conformance evidence does this release acceptance record reference?
  2. What expected and observed outcomes does this negative fixture evidence record report?
  3. What decision, authorized decision maker, rationale and applicable hold status does this acceptance record document?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise contract
Entry kind
contract
Domain
EnterpriseXCT
Industry
Cross-industry
Tags
EM-XCT-10W0contractModelRegistrationModelReleaseConformanceEvidencePublicationHold

What it is Filled

A release registration record identifies a model release and records its manifest, dependencies, fingerprints, conformance evidence, publication holds, acceptance decisions and withdrawal status.

Why it exists Filled

Support accountable acceptance and traceable use of model releases through explicit release identity, reproducibility evidence and recorded publication decisions.

Distinguishing features Filled

  • Pinned references alone do not guarantee exact reproducibility, which requires immutable release identification, retained and retrievable artifacts and dependencies, verified content digests and any required environment specifications.
  • A content digest identifies bytes, while a semantic fingerprint is the output of a declared versioned computation over specified semantic inputs under explicit equivalence rules.
  • Semantic fingerprint comparisons support only the equivalence claims justified by their recorded computation and equivalence rules.
  • A conformance claim requires evidence, and installability is not assurance.
  • An open hold blocks canonical status regardless of other checks.
  • A supporting source reference identifies a specific document and its version, publication date or immutable revision.

What robots and AI may and may not do Filled

Must not

  • Treat this contour as authority to run tests or change publication, hold, acceptance or withdrawal status.
  • Represent a release as accepted without a recorded decision from an authorized role.
  • Represent a release with an open publication hold as eligible for canonical status.
  • Treat installability or a recorded test result alone as sufficient evidence of conformance.
  • Treat a wildcard or branch reference as pinned.
  • Substitute a content digest for a semantic fingerprint or infer semantic equivalence without declared computation and equivalence rules.
  • Claim exact reproducibility without supporting evidence for the required artifacts, dependencies, digests and environment.
  • Treat a vague source label as an identifiable supporting document.

Only with a human decision

  • An authorized release acceptance role decides whether to grant canonical status.
  • An authorized publication governance role decides whether to open or lift a publication hold.
  • An authorized release owner decides whether to withdraw a release that others depend on.

May

  • Describe missing declarations, placeholders and mutable references in a concrete release manifest.
  • Assess the scope and limitations of a concrete release's recorded installation and conformance evidence.
  • Compare the expected and observed outcomes in a recorded fixture result.
  • Report a concrete release's recorded holds, acceptance decisions and withdrawal status.
  • Identify recorded dependencies on a concrete withdrawn release.

Moral aspects Filled

  • Users and agents rely on registered models, so false conformance claims spread errors widely.
  • Withdrawals must stay transparent so that past decisions remain explainable.

Who is affected

  • Model authors and maintainers
  • Agents and systems consuming registered models
  • Reviewers who accept releases

Owners Filled

Steward

The curator of the meta-model catalogue who answers for model registration, release and acceptance.

Master systems

  • Model registry
  • Source configuration files
  • Dependency lock files
  • Policy store

Links to other meta-models Filled

references

  • WM-XCT-013 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A model is identified by its registry identifier; a release by identifier, semantic version and content digest.
  • A publication hold is identified by its own identifier and the release it blocks.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Filled

  • A release record carries a semantic version, a digest, pinned dependencies and conformance evidence.
  • A release record can be confused with a source branch, a draft or a package that only installs.

Capabilities and actions required Filled

  • Exact release reproducibility can be claimed only when evidence demonstrates reconstruction from retained and retrievable artifacts and dependencies with verified content digests under the recorded environment requirements.
  • Dependents of a withdrawn release can be found and notified.

Hazards and failure modes required Filled

  • Moving references, mutable version labels or unavailable artifacts and dependencies can prevent exact release reproduction.
  • Placeholders can lead to premature canonical status.
  • Withdrawal can cause loss of the audit trail.

Standards and interfaces optional Filled

  • The Semantic Versioning 2.0.0 specification by Tom Preston-Werner defines version number conventions.
  • FIPS 180-4 from the National Institute of Standards and Technology defines SHA-256 for content digests.
  • PROV-O from the World Wide Web Consortium supports provenance of releases and their evidence.

Context of use required Filled

  • The model is used by maintainers of a shared model catalogue and by tools that install models.
  • The model applies to every publication and withdrawal of a model release.

Sources Filled

  1. Semantic Versioning 2.0.0: version identifiers and precedence rules
  2. W3C PROV/SKOS/SHACL/ODRL where applicable
  3. Practice of source connectors, versioned schemas and policy enforcement
  4. W3C PROV-O: The PROV Ontology - Checked live (HTTP 200) on 2026-10-07.
  5. W3C SKOS Simple Knowledge Organization System Reference - Checked live (HTTP 200) on 2026-10-07.
  6. W3C Shapes Constraint Language (SHACL) - Checked live (HTTP 200) on 2026-10-07.
  7. W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • What proves installable, and what proves assurance?
  • Which reference is immutable?
  • How to revoke a release without losing reproducibility?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published

Built from: enterprise/models/em-xct-10/brief.json, ver-cy/world-models/card-supplements/em-xct-10.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.