methods · weekly settlement scope

What the weekly settlement covers — and what it does not

A weekly capture-settlement loop checks that TrustNav’s own captures of six declared source families arrived on their declared schedules. Its scope is set by a ratified, versioned policy, and this page states that scope in the policy’s own terms — the six families, the inputs expressly not watched, what schedule freshness means, and what it cannot establish.

the six watched source families
  • co_dora_license — The Colorado DORA professional-licence file (the state's published licensee dataset).
    expected weekly (168h, 48h grace) · freshness bound 14 days
  • nppes_parent_cache — The CMS NPPES monthly bulk dissemination file (national provider identity), captured from the parent cache.
    expected monthly (720h, 120h grace) · freshness bound 45 days
  • oig_leie_parent_cache — The HHS OIG List of Excluded Individuals and Entities (LEIE), captured from the parent cache.
    expected monthly (720h, 120h grace) · freshness bound 45 days
  • pecos_parent_cache — The CMS PECOS public provider-enrollment extract (PPEF), captured from the parent cache.
    expected quarterly (2160h, 240h grace) · freshness bound 120 days
  • co_serff_filings — Colorado SERFF filings (plan filings and provider listings as filed).
    expected weekly (168h, 72h grace) · freshness bound 21 days
  • co_tic_mrf — Carrier Transparency-in-Coverage machine-readable rate files, Colorado slice.
    expected monthly (720h, 120h grace) · freshness bound 45 days
expressly not watched

The policy names what the loop does not watch, so absence from the list above is a stated boundary, not an oversight:

  • care_compare_ndf — CMS Care Compare / National Downloadable File inputs.
  • ghost_provider_audit_inputs — The ghost-provider audit inputs (the machinery behind the withdrawn Network Integrity findings).
  • queue_v0_legacy_ingestion — The legacy queue-era ingestion.
  • anything_outside_trustnav_co_schema — Any material outside the Colorado schema.

Many further sources are captured for custody (their bytes and hashes recorded) without being watched by this loop. Staging bytes can never silently widen what the loop claims to watch: adding a family to the watched set is a separate, governed policy re-ratification.

what schedule freshness means

Each watched family declares an expected capture cadence, a grace period, and a freshness bound. At each weekly settlement the loop records, per family, whether captures arrived against that schedule (captures recorded / captures scheduled) and the lag between settlement time and the newest capture. A family outside its bound is recorded as an open assertion, not silently skipped.

what it does not establish

The policy states the limits of its own metrics, and they are the important part. Freshness lag “does not capture publisher-side currency; a low lag against a stale source proves only our own promptness” — TrustNav-side capture freshness never establishes that the publisher’s content is current. Capture completeness “does not capture correctness or completeness of captured content; a 100% score is consistent with capturing wrong or stale artifacts on time.” The loop attests to the discipline of our own capturing, not to the state of any carrier’s or agency’s publishing.

settlement policy version

sentinel-policy.trustnav-co · policy_version 2 · weekly cadence · policy_content_hash 1e1632c3803aeead87f0af00c359bc3e3726aa9f618650bf31531c1023b70dc7

all method artifacts →the record →verify an edition →