Composition foundation and reconciliation of the ELMM role
Keep an enterprise landscape coherent and accountable by recording which model versions govern its subjects and how conflicting composition claims are resolved.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 4 findings · 10 questions
Composition boundary Defines the enterprise landscape scope and authority of one composition decision.
Decision scope
Identifies the enterprise subjects and accountable decision authority.
Scope and authority
Records the landscape boundary and decision mandate.
- Which enterprise landscape and subject boundary does this composition decision cover?
- Which enterprise role has authority to approve this composition decision?
Composition and resolution Records the model references and role assignments proposed or approved for the enterprise landscape.
Resolution contract
Identifies the referenced definitions and evidence supporting their use.
Reference resolution
Pins the model references and evidence relevant to the decision.
- Which model identifiers, versions and authoritative sources does this composition decision reference?
- Which dated verification evidence does this composition decision cite for the referenced models' availability and declared roles?
Landscape separation
Separates enterprise composition choices from changes to referenced model definitions.
- Which enterprise subject and composition role does this decision assign to each referenced model?
- Which boundary does this decision establish between enterprise composition choices and the definitions governed by referenced models?
Role decision Records conflicting claims, their disposition and the decision's lifecycle.
Boundary decision
Preserves the rationale and approval state of the composition decision.
Composition role decision
Records the enterprise disposition of proposed model roles without asserting unverified definitions.
- Which conflicting model role claims and supporting sources does this composition decision record?
- What disposition and rationale does this composition decision record for each disputed role?
- What approval status, approving authority and effective date does this composition decision record?
- Which unresolved conditions, review trigger and predecessor decision does this composition decision reference?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise foundation
- Entry kind
- foundation
- Domain
- EnterpriseKRN
- Industry
- Cross-industry
- Tags
- EM-KRN-01W0foundationCompositionResolutionContractKernelBoundaryDecision
What it is Filled
An enterprise composition decision record that identifies the model references used for a defined enterprise landscape and records their approved roles, boundaries and reconciliation decisions.
Why it exists Filled
Keep an enterprise landscape coherent and accountable by recording which model versions govern its subjects and how conflicting composition claims are resolved.
Distinguishing features Filled
- The subject is one enterprise composition decision with a defined landscape scope.
- The record references model definitions without changing their published meaning.
- Composition roles are supported by versioned evidence and explicit enterprise authority.
- Unresolved model roles remain pending and do not establish approved enterprise composition.
What robots and AI may and may not do Filled
Must not
- Treat a proposed composition decision as approved.
- Infer the meaning of an undefined model name or acronym.
- Assert that a referenced model is available or absent without versioned verification evidence.
- Resolve conflicting authoritative claims silently.
- Use an enterprise composition decision to redefine a referenced model.
Only with a human decision
- Obtain human approval before accepting or revising the enterprise composition decision.
- Refer unresolved model role conflicts to the accountable enterprise architecture authority.
- Obtain human approval before changing the decision's enterprise scope or delegated authority.
May
- Record the model references and enterprise roles stated in authorized decision evidence.
- Check whether the decision identifies versions, sources, scope and approval status.
- Flag conflicting role claims and draft a reconciliation proposal for the accountable enterprise role.
Moral aspects Filled
- Unsupported composition claims can cause enterprise agents to apply the wrong definitions.
- Unrecorded decisions can obscure accountability for effects on enterprise records and workflows.
- Conflicting evidence must remain visible until an authorized decision resolves it.
Who is affected
- Enterprise record owners rely on approved model boundaries.
- Enterprise architects are accountable for composition decisions.
- Implementers and agent users depend on consistent enterprise definitions.
Owners Filled
Steward
The enterprise architecture steward is accountable for model composition decisions within the enterprise landscape.
Master systems
- An architecture decision register maintains composition decisions and approvals.
- An enterprise model registry maintains referenced model identities and versions.
- An evidence repository maintains the sources supporting composition decisions.
- A policy register maintains decision authority and delegation rules.
Links to other meta-models Filled
neighbor
- EM-LND-01 - Organizational structure is a landscape object that must compose without kernel imports.
- EM-LND-06 - The software product landscape is another composed layer outside the kernel.
- EM-XCT-01 - Identity and external ID matching shares the reference resolution concern.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A composition decision has a stable identifier, revision and defined enterprise landscape scope.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- The record identifies referenced model versions, assigned roles, decision evidence and approval status.
- The record can be confused with a model specification or a proposal to change a shared standard.
Capabilities and actions required Filled
- The decision can explain why a referenced model has a particular role in the enterprise landscape.
- The decision can preserve disputed claims and trace their authorized disposition.
Hazards and failure modes required Filled
- Unverified model roles can cause incorrect interpretation of enterprise records.
- Unapproved decisions can be mistaken for active enterprise policy.
- Missing version evidence can conceal changes in the definitions used by enterprise agents.
Standards and interfaces optional Filled
- An enterprise model registry supplies authoritative model references.
- An architecture decision register supplies approval and supersession records.
Context of use required Filled
- The record applies to composition decisions within a defined enterprise landscape.
- Changes to a shared model or standard require a separate decision by its governing authority.
Sources Filled
- Current definitions of the Vercy kernel and semantic jurisdiction
- The declared PLMM role of ELMM and the MMDG requirements
- An architecture for resolving schemas and packages without importing domain vocabulary
- Vercy Specification - Checked live (HTTP 200) on 2026-10-07.
- Vercy Model Agent Protocol - Checked live (HTTP 200) on 2026-10-07.
- JSON Schema Specification - Checked live (HTTP 200) on 2026-10-07.
- Vercy Agent Bootstrap Contract - Checked live (HTTP 200) on 2026-10-07.
Open questions
- Which primitives already belong to the Vercy kernel?
- Is a separate ELMM needed, and what is its authority?
- How to reconcile contradictory descriptions in public documents?
- Согласовать runtime и repository версии AISMM/PLMM и роль ELMM; совместимость сейчас не доказана.
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-krn-01/brief.json, ver-cy/world-models/card-supplements/em-krn-01.json
Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.