EM-XCT-10 · Shared contract · W0
Model registration, versioning and acceptance
Research into the publication contract: manifest, role, schema, semantic version, digest, fingerprint, dependencies, holds and withdrawal.
Result published
Claude: complete-study-and-frozen-release-audits; Grok: complete-study-and-frozen-release-audits.
Published results
Research note, in Russian: The 0.1.0 release is immutable and accepted for its bounded profile. Future semantics require a new version.
Subject boundary and candidate types
- ModelRegistration
- ModelRelease
- ConformanceEvidence
- PublicationHold
Deep research questions
- What proves installable, and what proves assurance?
- Which reference is immutable?
- How to revoke a release without losing reproducibility?
Verifiable invariants
- Wildcard and main are not a lock
- A digest is not a semantic fingerprint
- Conformance requires evidence
End-to-end acceptance scenario
Verify a package with pinned refs, negative fixtures and an open hold: publication of canonical status is blocked.
Negative case
A TBD fingerprint and muc=Conformant are declared a finished registration.
Approaches to compare
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Candidates in the live catalogue
- WM-XCT-013 · Registry Pattern · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.