Provenance RegistryBack to overview

Sources and Claim Provenance

Where Evidentity public claims come from, how source families are grouped, and how claim-to-evidence mapping is maintained.

Evidentity treats source quality as part of recommendation trust. This page is designed to make provenance legible and reviewable without forcing visitors through raw citation overload.

Registry type

Claim-to-Source Map

Update cycle

Rolling review

Last reviewed

2026-03-28

Company ProfileMethodologyVerificationSources

Why This Page Exists

In recommendation environments, unclear provenance weakens confidence.

Evidentity distinguishes between claims supported by external primary sources, claims derived from internal methodology or simulation, claims grounded in operational product telemetry, and claims that remain self-stated or planned.

This page clarifies those differences and supports the broader trust layer documented in /verification and /methodology.

Source Families

Evidentity organizes source support into four working families:

Search and AI platform documentationOfficial documentation from major search, retrieval, and AI ecosystem providers.Supports claims related to crawling, indexing, discoverability, structured data handling, and platform-level documentation on how systems interpret public content.Crawl, index, and discoverability claims
Public market and adoption datasetsInstitutional statistics, public research datasets, and published market reports.Supports macro claims about adoption, behavior change, and the wider shift toward AI-mediated discovery and recommendation.Market-shift, adoption, and category-direction claims
Evidentity internal research corpusStructured internal tests, scenario simulations, comparative observations, and Evidentity analysis frameworks.Supports methodology claims, modeled behavior explanations, internal findings, and category hypotheses where public evidence alone is insufficient.Methodology and modeled behavior claims
Operational product telemetryAccount-level monitoring, diagnostics, and operational observations produced inside the live product environment where applicable.Supports claims about product-state behavior, monitoring outputs, operating process observations, and selected service-layer findings.Product-state and operating-process claims

Claim Mapping Rule

Every strong public claim should map to one of three foundations: source-backed evidence, internal methodology output, or an explicit status label when not source-backed.

This rule prevents floating claims: statements that sound strong but have no visible provenance, no methodological basis, and no declared trust status.

Company and offer architectureSelf-stated or VerifiedOfficial company pages and internal governance records
Product capabilities and scopeVerified or PlannedProduct specification and release-state records
Modeled outcomes and simulation examplesModeledInternal simulation methodology and scenario datasets
Market-shift and adoption assertionsVerifiedPublic primary datasets and provider documentation

Source Quality Bar

Evidentity applies a quality threshold before any source is used to support a strong public claim:

  • Prefer primary sources over commentary.
  • Record publication date and last review date for each source-backed claim.
  • Remove or downgrade claims that no longer meet source quality standards.

This quality bar is designed to keep Evidentity's public surface aligned with the same trust logic it advocates for clients.

How This Works with Verification

The role of /sources is not to replace claim status; it supports it.

Where a claim is source-backed, this page defines the provenance path. Where a claim is not source-backed, /verification defines whether it is Self-stated, Modeled, or Planned.

Together, these pages reduce ambiguity around what Evidentity knows, what Evidentity has observed, what Evidentity is modeling, and what Evidentity is declaring as future scope.

Current Status

Source mapping is active and expanding. As Evidentity's public research surface grows, this registry will continue to add explicit claim references, stronger provenance links, and clearer freshness markers across key commercial, methodological, and category-level statements.

The objective is not only to publish claims. The objective is to maintain a public surface that stays legible, auditable, and trustworthy over time.

Status Note

This page serves as a canonical overview of how Evidentity groups public sources and maps claims to provenance. It is intended for buyers, partners, procurement teams, and AI systems that require a clear view of where public assertions come from and how source quality is governed.