EM-PRD-04 · Subject model · W2
Research, hypothesis and experiment
Research question, hypothesis, experiment design, run and interpretation of the result. AI training and evaluation use specialized child models.
Partially published; research continues
Claude: complete-frozen-study-plus-one-audit-no-rerun; Grok: complete-exact-prompt-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
- ResearchStudy
- Hypothesis
- ExperimentDesign
- ExperimentRun
- ResearchFinding
Deep research questions
- Which conditions make a result reproducible?
- How to distinguish absence of effect from absence of data?
- How to link a negative result to a subsequent decision?
Verifiable invariants
- The hypothesis precedes result evaluation or is marked post-hoc
- A run pins the versions of its inputs
- A conclusion states its limits of applicability
End-to-end acceptance scenario
Two runs of one design with different inputs and contradictory results remain distinguishable and reproducible.
Negative case
A failed experiment is deleted and the hypothesis is replaced retroactively.
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-022 · Experiment / Trial · unversioned · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-KNW-009 · Hypothesis · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-036 · Research Study · 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.