World Models · Published

Model Composition Resolution

Resolve and verify a bounded exact composition of model releases for one sovereign Dimension, preserving authority, provenance and explicit runtime readiness.

AI YAMLAGENTS.mdResearch evidence
Published. Research assurance: reviewable-draft. The Codex + Claude + Grok synthesis is published for use and review with caution. It passed structural validation but is not yet a canonical Vercy release because the source and coverage holds below remain open.
Catalogue IDWM-XCT-040
Version0.1.0
Previous version-
Typepattern
ValidationPassed
Synthesis digestsha256:18634b2c75d3175d…
10Sources
6Bundles
12Layers
12Findings
36Questions
12Artifacts
Format-independent logical structure

Bundles to Layers to Findings to Questions + Artifacts

composition-bundle-scopeKernel and domain boundary2 layers

Kernel and domain boundary within the bounded composition episode.

composition-layer-boundaryBounded contract identity1 findings

One composition episode is owned by one Dimension; it reuses the kernel and does not import corporate domain models.

composition-plan

Bounded contract identity

One composition episode is owned by one Dimension; it reuses the kernel and does not import corporate domain models.

Questions
  1. What exactly is the subject of this composition episode?definition
    Expected answer
    • planId
    • dimensionId
    • revision
    • supersedes
  2. Which issuer owns this plan identity and its predecessor?identity
    Expected answer
    • planId
    • dimensionId
    • revision
    • supersedes
  3. Which concerns remain in the kernel or domain models?composition
    Expected answer
    • planId
    • dimensionId
    • revision
    • supersedes
Artifacts
  • Bounded contract identity evidencePlan fields planId, dimensionId, revision, supersedes and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-graphsThree independent graphs1 findings

Package closure is distinct from instance relationships and transport locations. A legal business cycle is not a mandatory package cycle.

composition-graph

Three independent graphs

Package closure is distinct from instance relationships and transport locations. A legal business cycle is not a mandatory package cycle.

Questions
  1. Which edges are mandatory package dependencies?relationship
    Expected answer
    • roots
    • releases.requires
    • releases.references
  2. Does the required graph contain a cycle or missing exact target?constraint
    Expected answer
    • roots
    • releases.requires
    • releases.references
  3. Which optional references must remain outside automatic closure?composition
    Expected answer
    • roots
    • releases.requires
    • releases.references
Artifacts
  • Three independent graphs evidencePlan fields roots, releases.requires, releases.references and a recorded validation or disposition; unknowns do not become successful checks.
composition-bundle-releasesRelease and content identity2 layers

Release and content identity within the bounded composition episode.

composition-layer-versionsExact immutable releases1 findings

Select one exact release per publisher-qualified ID. Do not collapse content digest, semantic fingerprint, SemVer and object revision.

composition-release

Exact immutable releases

Select one exact release per publisher-qualified ID. Do not collapse content digest, semantic fingerprint, SemVer and object revision.

Questions
  1. What exact model identifier and version are selected?identity
    Expected answer
    • modelId
    • version
    • semanticFingerprint
    • compatibility
  2. Do changed bytes reuse a previously selected release version?quality
    Expected answer
    • modelId
    • version
    • semanticFingerprint
    • compatibility
  3. What scoped evidence supports compatibility beyond a version label?interoperability
    Expected answer
    • modelId
    • version
    • semanticFingerprint
    • compatibility
Artifacts
  • Exact immutable releases evidencePlan fields modelId, version, semanticFingerprint, compatibility and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-bytesTransport integrity and origins1 findings

Descriptors pin every specification, agent guide and binding file. Local owner policy supplies trusted origins; matching bytes do not establish authorship.

composition-descriptor

Transport integrity and origins

Descriptors pin every specification, agent guide and binding file. Local owner policy supplies trusted origins; matching bytes do not establish authorship.

Questions
  1. Do specification and AGENTS bytes match their digests and sizes?evidence
    Expected answer
    • specification
    • agents
    • binding.runtime
  2. Can a source or path escape the permitted package boundary?security
    Expected answer
    • specification
    • agents
    • binding.runtime
  3. Which source URL and observation identify these bytes?provenance
    Expected answer
    • specification
    • agents
    • binding.runtime
Artifacts
  • Transport integrity and origins evidencePlan fields specification, agents, binding.runtime and a recorded validation or disposition; unknowns do not become successful checks.
composition-bundle-authorityAuthority and temporal validity2 layers

Authority and temporal validity within the bounded composition episode.

composition-layer-policyIndependent installation authority1 findings

The caller-supplied policy, not assertions within the plan, decides owner, actor, purpose, effective interval, model allowlist and draft permission.

composition-authority

Independent installation authority

The caller-supplied policy, not assertions within the plan, decides owner, actor, purpose, effective interval, model allowlist and draft permission.

Questions
  1. Which current owner policy authorizes this actor and purpose?authority
    Expected answer
    • authority
    • policyDigest
    • allowedModelIds
  2. Which model identifiers and assurance levels are allowed?access
    Expected answer
    • authority
    • policyDigest
    • allowedModelIds
  3. What happens when the plan tries to grant itself permission?exception
    Expected answer
    • authority
    • policyDigest
    • allowedModelIds
Artifacts
  • Independent installation authority evidencePlan fields authority, policyDigest, allowedModelIds and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-timeFreshness and current-state preconditions1 findings

Plan and policy are evaluated at one explicit time; exact starting lock bytes prevent stale application. Historical evaluation cannot authorize a new CLI write.

composition-time

Freshness and current-state preconditions

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
  1. At which valid time was this plan applicable?temporal
    Expected answer
    • createdAt
    • validUntil
    • baseLockDigest
    • provenance.recordedAt
  2. What changed between planning and activation?event
    Expected answer
    • createdAt
    • validUntil
    • baseLockDigest
    • provenance.recordedAt
  3. Which immutable revision corrects an earlier decision?lifecycle
    Expected answer
    • createdAt
    • validUntil
    • baseLockDigest
    • provenance.recordedAt
Artifacts
  • Freshness and current-state preconditions evidencePlan fields createdAt, validUntil, baseLockDigest, provenance.recordedAt and a recorded validation or disposition; unknowns do not become successful checks.
composition-bundle-bindingsBindings and validation scope2 layers

Bindings and validation scope within the bounded composition episode.

composition-layer-readinessSemantic and native readiness1 findings

A published semantic package is useful without a native schema. Native-bound requires an explicit scoped runtime binding tied to the exact specification.

composition-binding

Semantic and native readiness

A published semantic package is useful without a native schema. Native-bound requires an explicit scoped runtime binding tied to the exact specification.

Questions
  1. Is this release semantic-only or explicitly native-bound?state
    Expected answer
    • installationMode
    • binding
    • binding.forSpecificationDigest
  2. Which runtime fact paths and units are actually declared?requirement
    Expected answer
    • installationMode
    • binding
    • binding.forSpecificationDigest
  3. Which registry may contain a package with no native binding?classification
    Expected answer
    • installationMode
    • binding
    • binding.forSpecificationDigest
Artifacts
  • Semantic and native readiness evidencePlan fields installationMode, binding, binding.forSpecificationDigest and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-nestedNested data validation1 findings

V3 envelope validation is not nested domain validation. Structured snapshots require both a schema and a separately selected trusted companion check.

composition-nested

Nested data validation

V3 envelope validation is not nested domain validation. Structured snapshots require both a schema and a separately selected trusted companion check.

Questions
  1. Which validator checks nested and cross-record meaning?validation
    Expected answer
    • binding.instanceSchema
    • binding.companionValidator
    • binding.scope
  2. Can an empty or permissive schema falsely promote readiness?constraint
    Expected answer
    • binding.instanceSchema
    • binding.companionValidator
    • binding.scope
  3. How are untrusted downloaded validators prevented from auto-executing?process
    Expected answer
    • binding.instanceSchema
    • binding.companionValidator
    • binding.scope
Artifacts
  • Nested data validation evidencePlan fields binding.instanceSchema, binding.companionValidator, binding.scope and a recorded validation or disposition; unknowns do not become successful checks.
composition-bundle-executionExecution and recovery2 layers

Execution and recovery within the bounded composition episode.

composition-layer-stagingFresh-target staging and idempotency1 findings

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.

composition-staging

Fresh-target staging and idempotency

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
  1. Which action is reversible before the fresh target is activated?process
    Expected answer
    • receiptId
    • planDigest
    • status
    • committedAt
  2. Which exact receipt demonstrates a committed staging result?event
    Expected answer
    • receiptId
    • planDigest
    • status
    • committedAt
  3. What remains after a write failure or a competing writer?exception
    Expected answer
    • receiptId
    • planDigest
    • status
    • committedAt
Artifacts
  • Fresh-target staging and idempotency evidencePlan fields receiptId, planDigest, status, committedAt and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-bootstrapNew Dimension installation1 findings

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.

composition-bootstrap

New Dimension installation

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
  1. How is the startup minimum assembled without HR or ERP imports?composition
    Expected answer
    • nativeBoundModels
    • semanticOnlyModels
    • nativeControlValidation
  2. Which control and record checks pass for the assembled Dimension?validation
    Expected answer
    • nativeBoundModels
    • semanticOnlyModels
    • nativeControlValidation
  3. What data remains absent after a successful empty bootstrap?state
    Expected answer
    • nativeBoundModels
    • semanticOnlyModels
    • nativeControlValidation
Artifacts
  • New Dimension installation evidencePlan fields nativeBoundModels, semanticOnlyModels, nativeControlValidation and a recorded validation or disposition; unknowns do not become successful checks.
composition-bundle-governanceAdoption, disclosure and evolution2 layers

Adoption, disclosure and evolution within the bounded composition episode.

composition-layer-rightsMastership and projections1 findings

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.

composition-rights

Mastership and projections

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
  1. Who masters release meaning, chosen pins and execution evidence?ownership
    Expected answer
    • owner
    • masterSystem
    • classification
    • purpose
  2. Which parts of a real composition must remain private?privacy
    Expected answer
    • owner
    • masterSystem
    • classification
    • purpose
  3. What single object and purpose does a disclosed plan projection cover?access
    Expected answer
    • owner
    • masterSystem
    • classification
    • purpose
Artifacts
  • Mastership and projections evidencePlan fields owner, masterSystem, classification, purpose and a recorded validation or disposition; unknowns do not become successful checks.
composition-layer-migrationExplicit evolution and deferral1 findings

Changed pins, down-conversion and existing-Dimension migration require a separate reviewed procedure. ELMM, PLMM and AISMM are compared without inventing compatibility.

composition-migration

Explicit evolution and deferral

Changed pins, down-conversion and existing-Dimension migration require a separate reviewed procedure. ELMM, PLMM and AISMM are compared without inventing compatibility.

Questions
  1. Which change requires a new plan or explicit migration?lifecycle
    Expected answer
    • supersedes
    • migration-decision
    • crosswalk
    • retention-policy
  2. Which receipts and predecessor links must local retention preserve?retention
    Expected answer
    • supersedes
    • migration-decision
    • crosswalk
    • retention-policy
  3. Which ELMM or legacy-landscape capabilities remain deliberately deferred?decision
    Expected answer
    • supersedes
    • migration-decision
    • crosswalk
    • retention-policy
Artifacts
  • Explicit evolution and deferral evidencePlan fields supersedes, migration-decision, crosswalk, retention-policy and a recorded validation or disposition; unknowns do not become successful checks.

Publication holds

  • Bounded reference implementation, not universal company-model compatibility or enterprise production certification.
  • Existing-Dimension migration, publisher/reviewer authentication, corporate IAM and distributed/power-loss durability are outside this release.
  • Only JSON-compatible Vercy specification files and the commercial-company preset are supported.
  • Source standards were inspected to stated ledger scope; no normative conformance certification.
  • Claude independent open-web study timed out; completed frozen review is a different evidence mode. Final Grok large-bundle review had partial visibility; exact per-pass scopes remain public.

Deferred research

  • 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.

Соберите проверенный состав моделей

Контракт фиксирует версии, зависимости, полномочия и схемы данных для нового Измерения компании. Действующие Измерения требуют отдельной миграции.

Инструкция и ограничения · Подробная модель · Полный пакет 0.1.0 · Claude, Grok и протокол проверки

68 автоматических проверок и 3 сценария нового Измерения прошли испытания. Вложенная семантика проверяется отдельно от V3. Все примеры вымышленные.