EM-PRD-02 · Subject model · W1
Service and Service Model
The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.
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
- Service
- ServiceOffering
- ServiceConsumption
- ServiceDependency
Deep research questions
- How does a service differ from a product and a process?
- Can an internal service have no price?
- How is one service linked to several providers and implementations?
Verifiable invariants
- The consumer is not the technical API client
- A service does not contain a copy of the runtime
- The expected outcome is separated from the measured one
End-to-end acceptance scenario
Describe an HR service and a digital platform service with different implementations and a shared way of specifying the outcome.
Negative case
An API endpoint is automatically declared a business service.
Approaches to compare
- TM Forum SID: product/service/resource and commercial roles
- IDTA AAS: physical assets and composite descriptions
- Product management and engineering configuration; compare selected PLM and software practices
Candidates in the live catalogue
- WM-ACT-004 · Service · 0.2.0-legacy · not installed automatically
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.