Model Composition Resolution

Bounded contract identity

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

1. What exactly is the subject of this composition episode? definition
2. Which issuer owns this plan identity and its predecessor? identity
3. Which concerns remain in the kernel or domain models? composition

Three independent graphs

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

1. Which edges are mandatory package dependencies? relationship
2. Does the required graph contain a cycle or missing exact target? constraint
3. Which optional references must remain outside automatic closure? composition

Exact immutable releases

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

1. What exact model identifier and version are selected? identity
2. Do changed bytes reuse a previously selected release version? quality
3. What scoped evidence supports compatibility beyond a version label? interoperability

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.

1. Do specification and AGENTS bytes match their digests and sizes? evidence
2. Can a source or path escape the permitted package boundary? security
3. Which source URL and observation identify these bytes? provenance

Independent installation authority

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

1. Which current owner policy authorizes this actor and purpose? authority
2. Which model identifiers and assurance levels are allowed? access
3. What happens when the plan tries to grant itself permission? exception

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.

1. At which valid time was this plan applicable? temporal
2. What changed between planning and activation? event
3. Which immutable revision corrects an earlier decision? lifecycle

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.

1. Is this release semantic-only or explicitly native-bound? state
2. Which runtime fact paths and units are actually declared? requirement
3. Which registry may contain a package with no native binding? classification

Nested data validation

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

1. Which validator checks nested and cross-record meaning? validation
2. Can an empty or permissive schema falsely promote readiness? constraint
3. How are untrusted downloaded validators prevented from auto-executing? process

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.

1. Which action is reversible before the fresh target is activated? process
2. Which exact receipt demonstrates a committed staging result? event
3. What remains after a write failure or a competing writer? exception

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.

1. How is the startup minimum assembled without HR or ERP imports? composition
2. Which control and record checks pass for the assembled Dimension? validation
3. What data remains absent after a successful empty bootstrap? state

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.

1. Who masters release meaning, chosen pins and execution evidence? ownership
2. Which parts of a real composition must remain private? privacy
3. What single object and purpose does a disclosed plan projection cover? access

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.

1. Which change requires a new plan or explicit migration? lifecycle
2. Which receipts and predecessor links must local retention preserve? retention
3. Which ELMM or legacy-landscape capabilities remain deliberately deferred? decision