EM-DAT-06 · Subject model · W1
Report definition and release instance
Report specification, parameters, run, publication and artifact. A dashboard is a set of permitted projections or a view of an explicitly modeled aggregate.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-browser-study-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
- ReportDefinition
- ReportRun
- ReportArtifact
- PublicationRecord
- DashboardDefinition
Deep research questions
- What makes a release reproducible?
- How to account for corrections to an already published report?
- Which rights apply to aggregated values?
Verifiable invariants
- A run pins the definition and the input snapshot
- A corrected release does not overwrite the published one
- Aggregation does not cancel the disclosure policy
End-to-end acceptance scenario
Release a report, correct an input fact and repeat the release: both versions are explainable, the sensitive slice stays hidden.
Negative case
A single Projection combines arbitrary HR and financial objects without a rights check.
Approaches to compare
- W3C DCAT: dataset, distribution, catalog
- W3C PROV and Data Cube: provenance and observation
- SDMX and BI/data catalog practice: indicators, breakdowns, definitions and releases
Candidates in the live catalogue
- WM-REC-002 · Report / Statement · 0.2.0-legacy · not installed automatically
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-REC-001 · Document / Record · 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.