Semantic-ready
The source plugin marks the report semantic and declares its reporting grain. Field-level aggregation, mapping, and visibility rules still apply.
The standard
A connector is not automatically a semantic model
The library keeps report readiness explicit. A registered schema can be useful for catalog or lifecycle work without being promoted as a safely modeled analytical report.
Basic contract
The report is registered for catalog, lifecycle, or helper use. Metric Hive does not present it as a fully semantic analytical report.
Registered schema
The connector schema is known, but the source plugin does not mark this report semantic-ready. Missing declarations remain visibly missing.
Contract explorer
Inspect source reports and fields
Search by connector, report, dataset, entity, or grain. Select a report to load its field contract directly from the public Metric Hive catalog.
Loading the contract library
The first semantic-ready report will appear here.
Why this is the moat
Every new connector strengthens the shared model
The defensible asset is not a page count. It is a growing, testable map between provider schemas and stable business meaning that can power queries, exports, comparisons, and AI answers.
Source-specific evidence
Provider field names and report schemas stay visible, so canonicalization does not erase provenance or make unsupported equivalence claims.
Reusable business meaning
Canonical mappings let equivalent concepts become discoverable across sources while preserving report grain and source context.
Machine-readable guardrails
Aggregation and visibility policies are contract data, not prose. The same rules can govern product surfaces, exports, and generated explanations.
Read how the semantic layer uses these contracts
See how canonical entities, grain, date and currency behavior, query guardrails, and governed exports fit together across Metric Hive.