EM-TEC-04 · Subject model · W1
Environment, infrastructure and service instance
Deployed instance, environment, infrastructure resource, configuration item and technical topology. VM image, physical asset and product are kept separate.
Partially published; research continues
Claude: complete-frozen-study-and-audit-with-remediation; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- DeployedInstance
- RuntimeEnvironment
- InfrastructureResource
- ConfigurationItem
- HostingRelation
Deep research questions
- How to model ephemeral resources without losing history?
- When do a CI and a financial asset coincide?
- How to distinguish a logical cluster from its nodes?
Verifiable invariants
- An instance references an artifact version
- An observation has a time and a source
- An address change does not necessarily change identity
End-to-end acceptance scenario
Two regions, a shared cluster, a replaced node and a preserved service yield a correct historical impact graph.
Negative case
An IP address is used as the sole permanent identifier of a server.
Approaches to compare
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
Candidates in the live catalogue
- WM-SFT-010 · Runtime / Compute Environment · unversioned · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-SFT-002 · Deployed System · 0.2.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-039 · Managed IT Service Graph · 0.1.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
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.