Questions, Answered

Yes. The catalog reports 1,578,155 reviewed rows from a manually published NPPES-derived product with source data as of 2026-08-09. Provider rows are not publicly browsable.

It is the reconciled row count for the published California Type 1 dentist product definition, not a count of every California NPI or currently practicing dentist.

No product for those states is publicly published yet. Zero is a release-status signal, not a provider-population claim.

CMS NPPES monthly replacement files, weekly incrementals and deactivations, companion location and other-name files, and the NUCC taxonomy reference subject to permission and attribution requirements.

NPI, entity type, provider or organization name, primary taxonomy, source-reported practice geography, represented source date, and release evidence.

No. An NPI is an identifier. NPPES fields are source-reported and do not by themselves prove current practice, licensure, credentialing, availability, or purchase intent.

Source identities and checksums, schema and transform versions, row counts, quality results, samples, delivery artifacts, manifests, and immutable object keys.

No. The worker can prepare and submit a frozen candidate, but an authorized operator must publish or roll back.

No. Release objects are versioned and immutable. Publication changes an atomic pointer while preserving rollback history.

The full checkout-to-download flow is available for the published California dentist snapshot through secure Stripe checkout.

Yes. The representative release passed source, permission, policy, reproducibility, resource, quality, and operator-review gates. M3 adds secure commerce and delivery for that release.

No. Lookup, bulk enrichment, API keys, quotas, and webhooks are later phases and must reuse the same release semantics.