{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.profile.enterprise-model-release-acceptance","code":"enterprise-model-release-acceptance","url":"https://ver.cy/models/enterprise-model-release-acceptance/","name":"Enterprise Model Release Acceptance","alternateNames":["Assertion provenance","EM-XCT-10","Evidence and confidence"],"kind":"enterprise-profile","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"Enterprise profiles","category":"Cross-cutting context","entryKind":"companion-contract","plane":"","domain":["Enterprise","Provenance","Evidence"],"industry":["Cross-industry"],"navPath":"NAV.XCT","tags":["EM-XCT-10","provenance","evidence","assertion","confidence"],"facets":{}},"whatItIs":"A companion contract for a Company Dimension that registers immutable model releases, derives whether each is installable and canonical in a given context from evidence and holds, and withdraws releases from new use without deleting them.","purpose":"Register immutable model releases, derive context-qualified installability and assurance, gate canonical status with evidence and holds, and withdraw new use without destroying reproducibility.","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["Registers immutable model releases and decides, per context, whether one is installable and canonical.","Withdraws a release from new use without deleting it, so past results stay reproducible.","Ties canonical status to evidence and open holds rather than to a version number."],"structure":{"bundles":[{"id":"MRA-B1","name":"Release identity","description":"Govern release identity for an enterprise model release.","layers":[{"id":"MRA-L1","name":"Coordinates and immutability","description":"Separate and verify coordinates and immutability.","findings":[{"id":"MRA-F1","name":"Release coordinate","description":"Keep release coordinate explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which model and semantic version identify this release?","id":"MRA-Q1","kind":"evidence"},{"text":"Can the same coordinate ever point to different bytes?","id":"MRA-Q2","kind":"decision"}]},{"id":"MRA-F2","name":"Registration binding","description":"Keep registration binding explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which WM-XCT-013 entry and act register the release?","id":"MRA-Q3","kind":"evidence"},{"text":"Which authority created the immutable coordinate?","id":"MRA-Q4","kind":"decision"}]}]},{"id":"MRA-L2","name":"Byte and semantic identity","description":"Separate and verify byte and semantic identity.","findings":[{"id":"MRA-F3","name":"Package digest","description":"Keep package digest explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which digest verifies the exact released bytes?","id":"MRA-Q5","kind":"evidence"},{"text":"Does any mutable locator masquerade as the lock?","id":"MRA-Q6","kind":"decision"}]},{"id":"MRA-F4","name":"Semantic fingerprint","description":"Keep semantic fingerprint explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which pinned canonicalization profile produced the semantic fingerprint?","id":"MRA-Q7","kind":"evidence"},{"text":"Is the fingerprint kept distinct from package-byte identity?","id":"MRA-Q8","kind":"decision"}]}]}]},{"id":"MRA-B2","name":"Resolution and installability","description":"Govern resolution and installability for an enterprise model release.","layers":[{"id":"MRA-L3","name":"Exact closure","description":"Separate and verify exact closure.","findings":[{"id":"MRA-F5","name":"Resolution receipt","description":"Keep resolution receipt explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which WM-XCT-040 receipt proves mandatory closure resolution?","id":"MRA-Q9","kind":"evidence"},{"text":"Are all closure members digest-addressed?","id":"MRA-Q10","kind":"decision"}]},{"id":"MRA-F6","name":"Transitive retention","description":"Keep transitive retention explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which closure bytes must remain for historical replay?","id":"MRA-Q11","kind":"evidence"},{"text":"Can dependency withdrawal break a prior exact lock?","id":"MRA-Q12","kind":"decision"}]}]},{"id":"MRA-L4","name":"Target-context staging","description":"Separate and verify target-context staging.","findings":[{"id":"MRA-F7","name":"Staging context","description":"Keep staging context explicit, immutable where required, and independently verifiable.","questions":[{"text":"For which target context was the closure staged?","id":"MRA-Q13","kind":"evidence"},{"text":"Does a receipt from another context count?","id":"MRA-Q14","kind":"decision"}]},{"id":"MRA-F8","name":"Installability predicate","description":"Keep installability predicate explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which mechanical checks make the release installable here and now?","id":"MRA-Q15","kind":"evidence"},{"text":"Which quality or approval claims are explicitly excluded?","id":"MRA-Q16","kind":"decision"}]}]}]},{"id":"MRA-B3","name":"Assessment and evidence","description":"Govern assessment and evidence for an enterprise model release.","layers":[{"id":"MRA-L5","name":"Profile and tool pins","description":"Separate and verify profile and tool pins.","findings":[{"id":"MRA-F9","name":"Assessment profile","description":"Keep assessment profile explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which profile version and digest define the criteria?","id":"MRA-Q17","kind":"evidence"},{"text":"Can latest or an unpinned profile support assurance?","id":"MRA-Q18","kind":"decision"}]},{"id":"MRA-F10","name":"Tool identity","description":"Keep tool identity explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which tool versions and artifact digests executed the assessment?","id":"MRA-Q19","kind":"evidence"},{"text":"Can a tool name alone reproduce the result?","id":"MRA-Q20","kind":"decision"}]}]},{"id":"MRA-L6","name":"Fixtures and evidence","description":"Separate and verify fixtures and evidence.","findings":[{"id":"MRA-F11","name":"Negative fixtures","description":"Keep negative fixtures explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which frozen fixture set was executed and did every negative fail as expected?","id":"MRA-Q21","kind":"evidence"},{"text":"Where is the fixture outcome recorded?","id":"MRA-Q22","kind":"decision"}]},{"id":"MRA-F12","name":"Evidence sufficiency","description":"Keep evidence sufficiency explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which digest-addressed evidence supports every required kind?","id":"MRA-Q23","kind":"evidence"},{"text":"Is the assessment active rather than revoked or superseded?","id":"MRA-Q24","kind":"decision"}]}]}]},{"id":"MRA-B4","name":"Publication control","description":"Govern publication control for an enterprise model release.","layers":[{"id":"MRA-L7","name":"Holds and projection","description":"Separate and verify holds and projection.","findings":[{"id":"MRA-F13","name":"Scoped hold","description":"Keep scoped hold explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which canonical, new-install or discovery scope does this hold affect?","id":"MRA-Q25","kind":"evidence"},{"text":"Is it blocking or advisory and who may dispose it?","id":"MRA-Q26","kind":"decision"}]},{"id":"MRA-F14","name":"Projection precedence","description":"Keep projection precedence explicit, immutable where required, and independently verifiable.","questions":[{"text":"Does the catalogue reflect authoritative current predicates?","id":"MRA-Q27","kind":"evidence"},{"text":"How is a stale projection detected and corrected?","id":"MRA-Q28","kind":"decision"}]}]},{"id":"MRA-L8","name":"Withdrawal and history","description":"Separate and verify withdrawal and history.","findings":[{"id":"MRA-F15","name":"Withdrawal notice","description":"Keep withdrawal notice explicit, immutable where required, and independently verifiable.","questions":[{"text":"Which WM-XCT-013 act authorizes the notice and when is it effective?","id":"MRA-Q29","kind":"evidence"},{"text":"Which current eligibility and discovery scopes stop?","id":"MRA-Q30","kind":"decision"}]},{"id":"MRA-F16","name":"Non-destructive retention","description":"Keep non-destructive retention explicit, immutable where required, and independently verifiable.","questions":[{"text":"Are release bytes, evidence and the transitive closure retained?","id":"MRA-Q31","kind":"evidence"},{"text":"Can exact historical locks still resolve after withdrawal?","id":"MRA-Q32","kind":"decision"}]}]}]}]},"agentConduct":{"may":["Validate a release record and retain its evidence.","Report installability for a stated context."],"mustNot":["Grant operational permission because a release is accepted.","Delete a withdrawn release.","Mark a release canonical while a hold is open."],"requiresHuman":["Lifting a publication hold.","Withdrawing a release that installations depend on."]},"ethics":{"considerations":["Models shape how organizations see people and work; accepting a release is a decision someone must own.","Reproducibility of past decisions depends on keeping withdrawn releases available."],"affectedParties":["Organizations that install the model","People described by data structured with the model"]},"owners":{"steward":"The model publisher owns releases; the installing organization owns its acceptance decision.","roles":[],"masterSystems":["Model release registry","Evidence store for assessments"]},"relations":[{"target":"WM-XCT-013","type":"references","note":"0.3.0-research.1"},{"target":"WM-XCT-040","type":"references","note":"0.1.1"},{"target":"vr.wm-xct-012","type":"aligned"},{"target":"vr.wm-xct-026","type":"aligned"},{"target":"vr.wm-xct-028","type":"aligned"}],"interaction":{"identity":{"applicability":"required","items":["Release ID with version and specification digest, immutable."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A release record pins one model version by digest and lists assessments, holds and status."]},"capabilities":{"applicability":"required","items":["Validate the governed record and retain its evidence without conferring operational permission."]},"hazards":{"applicability":"required","items":["Installing an unassessed release.","Losing the ability to reproduce results after a withdrawal."]},"interfaces":{"applicability":"required","items":["Semantic Versioning.","Software supply-chain attestations such as SLSA provenance."]},"context":{"applicability":"required","items":["Adoption of Vercy model releases inside a Company Dimension."]}},"sources":[{"title":"Research record EM-XCT-10: independent provider studies, audits and reconciled findings","url":"https://ver.cy/enterprise/research/em-xct-10/","note":"Evidence behind the release; claims in the card trace to it."},{"title":"Enterprise Model Release Acceptance 0.1.0 specification","url":"https://ver.cy/models/enterprise-model-release-acceptance/versions/0.1.0/spec.json","note":"Normative release, digest sha256:98fd24d78876c44cbe453eedaae78e26448a393b5aaf9110d95861c5c64d28cb"}],"openQuestions":["Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits. Use as a bounded reference gate with authoritative external registry, resolver and profile inputs. Do not treat fixture defaults, catalogue flags or labels as production proof. Required reading: https://ver.cy/models/enterprise-model-release-acceptance/versions/0.1.0/publication-addendum.md"],"resources":{"spec":"/models/enterprise-model-release-acceptance/versions/0.1.0/spec.json","agents":"/models/enterprise-model-release-acceptance/versions/0.1.0/AGENTS.md","package":"/models/enterprise-model-release-acceptance/versions/0.1.0/enterprise-model-release-acceptance-0.1.0.zip","source":"https://ver.cy/enterprise/research/em-xct-10/"},"provenance":{"origin":"enterprise research","builtFrom":["models/enterprise-model-release-acceptance/versions/0.1.0/spec.json","models/enterprise-model-release-acceptance/catalogue-entry.json","ver-cy/world-models/card-supplements/enterprise-model-release-acceptance.json"],"providers":["Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: it has no physical body to measure.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}