Home/Data & Methodology/Sources
Sources

Public records first. Derived fields labeled.

RateFileAI’s current filing research starts from public regulator records and available filing documents. Acquisition, extraction, normalization, and analysis are different stages with different failure modes.

Source path

  1. Acquire a public filing record or document.
  2. Retain its jurisdiction, filing identifier, dates, status, and source route.
  3. Normalize fields into a shared schema without replacing the original value.
  4. Label calculations, classifications, inferences, and user conclusions separately.

Variable coverage A missing record has more than one explanation

Regulator access, acquisition freshness, held-corpus scope, document availability, extraction coverage, and source changes can all affect what is present. Filing silence is not presented as proof that nothing changed.

basis definitions: methodology artifactsMethodology →

Current public producer artifacts

Open the machine-readable contracts directly. Each consumer must still validate its version, provenance where supplied, and freshness.

Coverage authority

Observed held records and within-held field presence by jurisdiction.

Open JSON →

Methodology manifest

A separately published methodology snapshot with its own basis.

Open JSON →

Definitions dictionary

Product-inward field and metric definitions when current.

Open JSON →

Data Trust contract boundary

No protection, dimension, latency, completeness, or source claim is inferred without a named governed producer and as-of contract.

Data Trust mapped requirement availability
RequirementStateCurrent producer or boundary
Source route contractUNAVAILABLENo governed Data Trust source contract returns this mapped field on the current surface; unknown, stale, null, and producer-pending states remain explicit.