Enterprise landscape
A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.
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 → 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 landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-18W3landscapeEnterpriseLandscapeEnterpriseViewScope
What it is Filled
A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.
Why it exists Filled
A composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.
Distinguishing features Derived, awaiting review
- The composition is chosen explicitly
- Ownership of facts stays in the domains
- A cross-context transition preserves restrictions
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: The enterprise is obliged to install every subject model from the registry.
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
- EnterpriseLandscape
- EnterpriseViewScope
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
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
Open questions
- Which questions justify including each contour?
- How to act when local meanings conflict?
- How to assess completeness without mandatorily installing all domains?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-18/brief.json
Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.