← Back to catalogue
Research draft

Composition foundation and reconciliation of the ELMM role

EM-KRN-01 · em-krn-01

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.

Enterprise profiles Enterprise foundation EnterpriseKRN

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Missing, in the backlog

Not described yet. This gap is in the card backlog.

Note: Research contour: bundles not designed yet; questions are listed as open questions.

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise foundation
Entry kind
foundation
Domain
EnterpriseKRN
Industry
Cross-industry
Tags
EM-KRN-01W0foundationCompositionResolutionContractKernelBoundaryDecision

What it is Filled

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.

Why it exists Filled

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.

Distinguishing features Derived, awaiting review

  • The kernel does not depend on domain models
  • The Enterprise Landscape is separated
  • An unverified ELMM does not become installable

What robots and AI may and may not do Derived, awaiting review

Must not

  • Negative case: The kernel imports Employee, Product and Contract for the sake of universality.

Note: Negative case of the research brief, not yet a rule for agents.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

Куратор мета-моделей Vercy

Master systems

  • Реестр моделей
  • sources.yaml
  • vercy.lock
  • политики

Links to other meta-models Missing, in the backlog

Not described yet. This gap is in the card backlog.

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Derived, awaiting review

  • CompositionResolutionContract
  • KernelBoundaryDecision

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Context of use required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Sources Filled

  1. Current definitions of the Vercy kernel and semantic jurisdiction
  2. The declared PLMM role of ELMM and the MMDG requirements
  3. An architecture for resolving schemas and packages without importing domain vocabulary

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

Card as JSON Source Card backlog vercy.card/1

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-krn-01/brief.json

Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.