EM-PRD-01 · Subject model · W1
Product, Offering and Roadmap
The product as a managed outcome for a consumer, offering variants, prices and development intents. The physical instance, the software and the actual delivery have separate boundaries.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Product
- ProductFamily
- Offering
- PricePlan
- RoadmapItem
Deep research questions
- When does an edition continue a product, and when does it form a new one?
- How is a roadmap promise separated from a contractual obligation?
- How are a free, an internal and a physical product described on one foundation?
Verifiable invariants
- An offering has a market and a period
- A price has a currency and a unit
- A roadmap item does not prove the existence of a feature
End-to-end acceptance scenario
Map SaaS, a device and an internal product: the shared meaning is preserved, and the profile does not impose a subscription on the device.
Negative case
A single pricing change creates a new software product.
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-ECO-021 · Offer / Quote · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-008 · Plan / Schedule · 0.3.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.