EM-KRN-01 · Composition foundation · W0
Composition foundation and reconciliation of the ELMM role
Investigate the boundary between the Vercy kernel, the declared ELMM composition kernel and the Enterprise Landscape. ELMM is absent from the verified runtime: this is an assignment, not a finished package.
Partially published; research continues
Claude: complete-full-file-audit-and-focused-remediation-review; Grok: complete-independent-study-audits-and-remediation-review.
Published results
Research note, in Russian: Existing-Dimension transactional migration; ELMM/MVS/context budgeting and semantic fingerprints; authenticated publisher/reviewer claims; full native bindings for domain families. Current release is a tested new-commercial-company-Dimension reference only.
Subject boundary and candidate types
- CompositionResolutionContract
- KernelBoundaryDecision
Deep research 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?
Verifiable invariants
- The kernel does not depend on domain models
- The Enterprise Landscape is separated
- An unverified ELMM does not become installable
End-to-end acceptance scenario
Show reference resolution without domain imports, a separate Enterprise Landscape and a documented reuse/extend/defer decision on ELMM.
Negative case
The kernel imports Employee, Product and Contract for the sake of universality.
Approaches to compare
- 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
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.