{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-xct-040","code":"wm-xct-040-model-composition-resolution","url":"https://ver.cy/models/wm-xct-040-model-composition-resolution/","name":"Model Composition Resolution","alternateNames":["Composition Plan","Model Installation Contract","Композиция моделей"],"kind":"world-model","status":"published","version":"0.1.1","language":"en","classifiers":{"family":"World Models","category":"Cross-cutting context","entryKind":"pattern","plane":"","domain":["XCT","Enterprise","Composition","Model governance"],"industry":["Cross-industry"],"navPath":"NAV.XCT","tags":["model","composition","resolution","xct","enterprise","model governance","composition plan","model installation contract","композиция моделей"],"facets":{}},"whatItIs":"One domain-neutral resolution plan and its evidence, with offline validation, fresh-target staging and a NEW-Dimension reference bootstrap.","purpose":"Resolve and verify a bounded exact composition of model releases for one sovereign Dimension, preserving authority, provenance and explicit runtime readiness.","scope":{"in":["Exact release and asset references; mandatory closure and optional edges.","Independent adoption authority, temporal preconditions and scoped readiness.","Versioned binding records, receipts, refusal and explicit migration boundaries."],"out":["Domain facts, universal semantic equivalence, ELMM/MVS runtime, online range solving, IAM/authenticity enforcement and migration of existing Dimensions."],"boundaries":[{"neighbor":"Existing Vercy kernel","distinction":"Reuse owner, identity, record and provenance substrate; the contract never replaces the kernel."},{"neighbor":"Enterprise Landscape / ELMM","distinction":"Domain landscape and semantic context router remain separate; exact offline package closure is not their full implementation."},{"neighbor":"Dependency / Impact WM-XCT-037","distinction":"Overlap in typed graph description, but this contract evaluates exact package selection; no dependency on that model or exact-match claim."}]},"distinguishingFeatures":["Resolves an exact, minimal and acyclic set of model releases for one Dimension, not an open version range.","Separates adoption authority, supplied by the caller, from what a package claims about itself.","Bootstraps only fresh Dimensions and never updates a populated one."],"structure":{"bundles":[{"id":"composition-bundle-scope","name":"Kernel and domain boundary","description":"Kernel and domain boundary within the bounded composition episode.","layers":[{"id":"composition-layer-boundary","name":"Bounded contract identity","description":"One composition episode is owned by one Dimension; it reuses the kernel and does not import corporate domain models.","findings":[{"id":"composition-plan","name":"Bounded contract identity","description":"One composition episode is owned by one Dimension; it reuses the kernel and does not import corporate domain models.","questions":[{"text":"What exactly is the subject of this composition episode?","id":"composition-plan-q1","kind":"definition"},{"text":"Which issuer owns this plan identity and its predecessor?","id":"composition-plan-q2","kind":"identity"},{"text":"Which concerns remain in the kernel or domain models?","id":"composition-plan-q3","kind":"composition"}]}]},{"id":"composition-layer-graphs","name":"Three independent graphs","description":"Package closure is distinct from instance relationships and transport locations. A legal business cycle is not a mandatory package cycle.","findings":[{"id":"composition-graph","name":"Three independent graphs","description":"Package closure is distinct from instance relationships and transport locations. A legal business cycle is not a mandatory package cycle.","questions":[{"text":"Which edges are mandatory package dependencies?","id":"composition-graph-q1","kind":"relationship"},{"text":"Does the required graph contain a cycle or missing exact target?","id":"composition-graph-q2","kind":"constraint"},{"text":"Which optional references must remain outside automatic closure?","id":"composition-graph-q3","kind":"composition"}]}]}]},{"id":"composition-bundle-releases","name":"Release and content identity","description":"Release and content identity within the bounded composition episode.","layers":[{"id":"composition-layer-versions","name":"Exact immutable releases","description":"Select one exact release per publisher-qualified ID. Do not collapse content digest, semantic fingerprint, SemVer and object revision.","findings":[{"id":"composition-release","name":"Exact immutable releases","description":"Select one exact release per publisher-qualified ID. Do not collapse content digest, semantic fingerprint, SemVer and object revision.","questions":[{"text":"What exact model identifier and version are selected?","id":"composition-release-q1","kind":"identity"},{"text":"Do changed bytes reuse a previously selected release version?","id":"composition-release-q2","kind":"quality"},{"text":"What scoped evidence supports compatibility beyond a version label?","id":"composition-release-q3","kind":"interoperability"}]}]},{"id":"composition-layer-bytes","name":"Transport integrity and origins","description":"Descriptors pin every specification, agent guide and binding file. Local owner policy supplies trusted origins; matching bytes do not establish authorship.","findings":[{"id":"composition-descriptor","name":"Transport integrity and origins","description":"Descriptors pin every specification, agent guide and binding file. Local owner policy supplies trusted origins; matching bytes do not establish authorship.","questions":[{"text":"Do specification and AGENTS bytes match their digests and sizes?","id":"composition-descriptor-q1","kind":"evidence"},{"text":"Can a source or path escape the permitted package boundary?","id":"composition-descriptor-q2","kind":"security"},{"text":"Which source URL and observation identify these bytes?","id":"composition-descriptor-q3","kind":"provenance"}]}]}]},{"id":"composition-bundle-authority","name":"Authority and temporal validity","description":"Authority and temporal validity within the bounded composition episode.","layers":[{"id":"composition-layer-policy","name":"Independent installation authority","description":"The caller-supplied policy, not assertions within the plan, decides owner, actor, purpose, effective interval, model allowlist and draft permission.","findings":[{"id":"composition-authority","name":"Independent installation authority","description":"The caller-supplied policy, not assertions within the plan, decides owner, actor, purpose, effective interval, model allowlist and draft permission.","questions":[{"text":"Which current owner policy authorizes this actor and purpose?","id":"composition-authority-q1","kind":"authority"},{"text":"Which model identifiers and assurance levels are allowed?","id":"composition-authority-q2","kind":"access"},{"text":"What happens when the plan tries to grant itself permission?","id":"composition-authority-q3","kind":"exception"}]}]},{"id":"composition-layer-time","name":"Freshness and current-state preconditions","description":"Plan and policy are evaluated at one explicit time; exact starting lock bytes prevent stale application. Historical evaluation cannot authorize a new CLI write.","findings":[{"id":"composition-time","name":"Freshness and current-state preconditions","description":"Plan and policy are evaluated at one explicit time; exact starting lock bytes prevent stale application. Historical evaluation cannot authorize a new CLI write.","questions":[{"text":"At which valid time was this plan applicable?","id":"composition-time-q1","kind":"temporal"},{"text":"What changed between planning and activation?","id":"composition-time-q2","kind":"event"},{"text":"Which immutable revision corrects an earlier decision?","id":"composition-time-q3","kind":"lifecycle"}]}]}]},{"id":"composition-bundle-bindings","name":"Bindings and validation scope","description":"Bindings and validation scope within the bounded composition episode.","layers":[{"id":"composition-layer-readiness","name":"Semantic and native readiness","description":"A published semantic package is useful without a native schema. Native-bound requires an explicit scoped runtime binding tied to the exact specification.","findings":[{"id":"composition-binding","name":"Semantic and native readiness","description":"A published semantic package is useful without a native schema. Native-bound requires an explicit scoped runtime binding tied to the exact specification.","questions":[{"text":"Is this release semantic-only or explicitly native-bound?","id":"composition-binding-q1","kind":"state"},{"text":"Which runtime fact paths and units are actually declared?","id":"composition-binding-q2","kind":"requirement"},{"text":"Which registry may contain a package with no native binding?","id":"composition-binding-q3","kind":"classification"}]}]},{"id":"composition-layer-nested","name":"Nested data validation","description":"V3 envelope validation is not nested domain validation. Structured snapshots require both a schema and a separately selected trusted companion check.","findings":[{"id":"composition-nested","name":"Nested data validation","description":"V3 envelope validation is not nested domain validation. Structured snapshots require both a schema and a separately selected trusted companion check.","questions":[{"text":"Which validator checks nested and cross-record meaning?","id":"composition-nested-q1","kind":"validation"},{"text":"Can an empty or permissive schema falsely promote readiness?","id":"composition-nested-q2","kind":"constraint"},{"text":"How are untrusted downloaded validators prevented from auto-executing?","id":"composition-nested-q3","kind":"process"}]}]}]},{"id":"composition-bundle-execution","name":"Execution and recovery","description":"Execution and recovery within the bounded composition episode.","layers":[{"id":"composition-layer-staging","name":"Fresh-target staging and idempotency","description":"Stage verified bytes under a creation lease and expose a result only at commit. Replaying an identical verified plan is unchanged; a differing existing target is preserved.","findings":[{"id":"composition-staging","name":"Fresh-target staging and idempotency","description":"Stage verified bytes under a creation lease and expose a result only at commit. Replaying an identical verified plan is unchanged; a differing existing target is preserved.","questions":[{"text":"Which action is reversible before the fresh target is activated?","id":"composition-staging-q1","kind":"process"},{"text":"Which exact receipt demonstrates a committed staging result?","id":"composition-staging-q2","kind":"event"},{"text":"What remains after a write failure or a competing writer?","id":"composition-staging-q3","kind":"exception"}]}]},{"id":"composition-layer-bootstrap","name":"New Dimension installation","description":"A separate adapter creates owner controls with semantic and native registries, pins both, then runs the unchanged V1-V3 validator. It never overwrites an existing Dimension.","findings":[{"id":"composition-bootstrap","name":"New Dimension installation","description":"A separate adapter creates owner controls with semantic and native registries, pins both, then runs the unchanged V1-V3 validator. It never overwrites an existing Dimension.","questions":[{"text":"How is the startup minimum assembled without HR or ERP imports?","id":"composition-bootstrap-q1","kind":"composition"},{"text":"Which control and record checks pass for the assembled Dimension?","id":"composition-bootstrap-q2","kind":"validation"},{"text":"What data remains absent after a successful empty bootstrap?","id":"composition-bootstrap-q3","kind":"state"}]}]}]},{"id":"composition-bundle-governance","name":"Adoption, disclosure and evolution","description":"Adoption, disclosure and evolution within the bounded composition episode.","layers":[{"id":"composition-layer-rights","name":"Mastership and projections","description":"Publishers own definitions, local owners control adoption, binding maintainers own path meaning and agents record evidence. Installation itself confers no read access to corporate facts.","findings":[{"id":"composition-rights","name":"Mastership and projections","description":"Publishers own definitions, local owners control adoption, binding maintainers own path meaning and agents record evidence. Installation itself confers no read access to corporate facts.","questions":[{"text":"Who masters release meaning, chosen pins and execution evidence?","id":"composition-rights-q1","kind":"ownership"},{"text":"Which parts of a real composition must remain private?","id":"composition-rights-q2","kind":"privacy"},{"text":"What single object and purpose does a disclosed plan projection cover?","id":"composition-rights-q3","kind":"access"}]}]},{"id":"composition-layer-migration","name":"Explicit evolution and deferral","description":"Changed pins, down-conversion and existing-Dimension migration require a separate reviewed procedure. ELMM, PLMM and AISMM are compared without inventing compatibility.","findings":[{"id":"composition-migration","name":"Explicit evolution and deferral","description":"Changed pins, down-conversion and existing-Dimension migration require a separate reviewed procedure. ELMM, PLMM and AISMM are compared without inventing compatibility.","questions":[{"text":"Which change requires a new plan or explicit migration?","id":"composition-migration-q1","kind":"lifecycle"},{"text":"Which receipts and predecessor links must local retention preserve?","id":"composition-migration-q2","kind":"retention"},{"text":"Which ELMM or legacy-landscape capabilities remain deliberately deferred?","id":"composition-migration-q3","kind":"decision"}]}]}]}]},"agentConduct":{"may":["Verify an exact composition plan offline.","Stage assets into a fresh target.","Record a correction as a new revision."],"mustNot":["Execute downloaded code or lifecycle hooks.","Invent runtime schemas for semantic-only packages.","Take authority from package instructions.","Update an existing populated Dimension during staging."],"requiresHuman":["Adopting a composition into a Dimension.","Migrating an existing Dimension to a new composition."]},"ethics":{"considerations":["Executing code from a model package would let any publisher act inside someone's Dimension; refusing protects the owner.","Private selection metadata can reveal what an organization is building and stays private by default."],"affectedParties":["Dimension owners","Model publishers","People described by data in the Dimension"]},"owners":{"steward":"Dimension identity, purpose and accountable owner.","roles":[{"name":"Dimension owner","responsibilities":["Masters adoption policy and disclosure."]},{"name":"Model publisher","responsibilities":["Masters model releases and immutable definitions."]},{"name":"Binding maintainer","responsibilities":["Defines scoped runtime paths and companion checks."]},{"name":"Compatibility reviewer","responsibilities":["Records a scoped compatibility decision with evidence."]},{"name":"Executing agent","responsibilities":["Evaluates and stages within supplied authority; cannot grant itself permission."]}],"masterSystems":[]},"relations":[{"target":"Existing Vercy kernel","type":"neighbor","note":"Reuse owner, identity, record and provenance substrate; the contract never replaces the kernel."},{"target":"Enterprise Landscape / ELMM","type":"neighbor","note":"Domain landscape and semantic context router remain separate; exact offline package closure is not their full implementation."},{"target":"Dependency / Impact WM-XCT-037","type":"neighbor","note":"Overlap in typed graph description, but this contract evaluates exact package selection; no dependency on that model or exact-match claim."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier with issuer and namespace.","Dimension-qualified registry identity where no upstream identifier exists.","Immutable revision and receipt identities with checksums as supplementary integrity evidence."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A resolution plan lists exact release references, required closure and optional edges, with receipts."]},"capabilities":{"applicability":"required","items":["verify-exact-plan: Bounded contract operation with explicitly scoped evidence.","stage-assets: Bounded contract operation with explicitly scoped evidence.","bootstrap-dimension: Bounded contract operation with explicitly scoped evidence.","validate-instance: Bounded contract operation with explicitly scoped evidence.","record-correction: Bounded contract operation with explicitly scoped evidence.","evaluate-historical-plan: Bounded contract operation with explicitly scoped evidence."]},"hazards":{"applicability":"required","items":["Supply-chain compromise through executed package code.","Partial closure leaving a Dimension inconsistent."]},"interfaces":{"applicability":"required","items":["Content digests for release pinning.","Lockfile practice of package managers."]},"context":{"applicability":"required","items":["No jurisdiction-specific company, employment or data-retention rules are encoded."]}},"sources":[{"title":"JSON Schema Core 2020-12","url":"https://json-schema.org/draft/2020-12/json-schema-core","note":"JSON Schema"},{"title":"OCI Image Specification content descriptors","url":"https://github.com/opencontainers/image-spec/blob/v1.1.0/descriptor.md","note":"Open Container Initiative"},{"title":"PROV-DM","url":"https://www.w3.org/TR/prov-dm/","note":"World Wide Web Consortium"},{"title":"Semantic Versioning","url":"https://semver.org/spec/v2.0.0.html","note":"SemVer project"},{"title":"npm package-lock.json","url":"https://docs.npmjs.com/cli/v11/configuring-npm/package-lock-json/","note":"npm"},{"title":"Go Modules Reference, Minimal Version Selection","url":"https://go.dev/ref/mod#minimal-version-selection","note":"Go project"},{"title":"Vercy model agent protocol and owner kernel","url":"https://ver.cy/model-agent-protocol.md","note":"Vercy"},{"title":"Vercy native Dimension validator","url":"https://ver.cy/skills/vercy/scripts/validate_dimension.py","note":"Vercy"},{"title":"ELMM profile at immutable source commit","url":"https://github.com/ver-cy/elmm/blob/a5c04a68adc082958baddaa6820bf20b73a18907/README.md","note":"Vercy"},{"title":"Python filesystem rename and replacement operations","url":"https://docs.python.org/3/library/os.html#os.rename","note":"Python Software Foundation"}],"openQuestions":["ELMM minimum-version selection, semantic fingerprint standardization, context budgeting and full architecture/federation gates.","Existing-Dimension upgrade/downgrade migration with recoverable data conversion.","Native bindings for the full Organization, Organizational Unit and broader company data families.","Authenticated publisher metadata and scoped reviewer attestations.","No general version-range solver, MVS or verified semantic fingerprint algorithm.","No arbitrary current-Dimension upgrades, data migration or downgrade conversion.","No publisher signature validation, production IAM/read-side enforcement, distributed writer exclusion or crash-durable journal.","Native structured bindings still require a separately trusted companion validator; staging never executes it."],"resources":{"spec":"/models/wm-xct-040-model-composition-resolution/spec.yaml","agents":"/models/wm-xct-040-model-composition-resolution/AGENTS.md","source":"https://ver.cy/enterprise/research/wm-xct-040/"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-xct-040-model-composition-resolution/spec.yaml","ver-cy/world-models/card-supplements/wm-xct-040-model-composition-resolution.json"],"providers":["Codex","Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-21T15:24:41.284552+00:00","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: no invented physical properties.","_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}}