Name the artifact. Name the basis. Keep the gaps.
The methodology manifest and coverage authority describe different populations. Values below load from the manifest only; current coverage remains a separately labeled route.
Readable for business users and technical diligence teams.
The page names the artifact, basis, source, as-of, and limitations so a business reader can use the result and a diligence reader can retrace what supports it.
Current methodology manifest
Loading current manifest as-of…
Two-denominator rule
The methodology corpus, the current Search corpus, and the coverage-authority holdings snapshot may differ. This page does not collapse them into one number. Each consumer keeps its own source and as-of.
Rate-field rule
The stated-rate denominator is the population reporting a stated rate. A filing that cannot state a rate is not counted as a zero-percent change. Any average is unweighted unless explicitly labeled otherwise.
Data sources and temporal change
The current methodology distinguishes public regulator records, rights-qualified public reports, source capture time, filing dates, effective dates, dispositions, and version lineage. Change detection is limited to fields and source records the producer can support; absence is not a claim that no change occurred.
Expert detail
The methodology corpus, Search corpus, and coverage-authority snapshot retain separate denominators and as-of values. Rate fields use the population reporting a stated rate; missing rate fields are not zero. Derived outputs name formula, unit, scope, provenance, and null handling when available.
Use the source-supported meaning, and keep the gaps visible.
These terms describe the current public-record methodology. They do not extend a filing record into an underwriting, legal, or operating conclusion.
Events and identities
- Filing event
- A source-backed filing record or change event supplied by the producer; it is not proof that operating behavior changed.
- Carrier group
- A normalized carrier-family grouping only where the current source/entity mapping supports it; unresolved relationships remain unavailable.
- Form event
- A source-backed form occurrence with filing, version, effective, or jurisdiction context where supplied; an absent event is not evidence of no form change.
- Objection
- An objection record, letter, response, or disposition only when the source documents expose it; no complete regulatory history is implied.
- Product naming
- Product or program names are preserved or normalized only when the source record provides them; names are not inferred from a similar record.
Time, comparison, and scope
- Refresh cycles
- Published freshness manifests describe a source/as-of snapshot and age. They are not an end-to-end regulator-latency or completeness promise.
- Eligibility
- An eligibility topic or criterion is shown only when the filing source supports it; it does not establish underwriting eligibility outside that record.
- Amendment and repeated change
- Version lineage, amendments, and repeated events are reported when the source producer supports them; absence is not a claim that no change occurred.
- Intelligence view
- A named view assembled from source-supported fields and deterministic transformations with its scope and basis retained; it is not an unsupported recommendation.
- Comparisons, trends, and materiality
- These views use named scope, basis, and source-supported fields. A trend is not a forecast, and materiality or a major-change label remains unavailable without a supported rule or producer.
- Major changes
- A major-change label is shown only when the supported change producer and rule identify it; missing evidence remains unavailable.
- Licensed third-party sources
- Rights-qualified public reports may add attributed context; rights, freshness, and coverage vary, and proprietary or unlicensed data is not implied.