Why This Page Exists
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 explains how those source classes are grouped and how they support the broader trust framework documented in /verification and /methodology.
Source Families
Evidentity organizes source support into four working families.
Search and AI platform documentation. Official documentation from major search, retrieval, and AI ecosystem providers.
Used to support claims related to crawling, indexing, discoverability, structured data handling, and platform-level guidance on how systems interpret public content.
Public market and adoption datasets. Institutional statistics, public research datasets, and published market reports.
Used to support macro claims about adoption, behavioural change, and the broader shift toward AI-mediated discovery and recommendation.
Evidentity internal research corpus. Structured internal tests, scenario simulations, comparative observations, and Evidentity analytical frameworks.
Used to support methodology claims, modeled behaviour explanations, internal findings, and category-level hypotheses where external evidence alone does not fully explain the operating logic.
Operational product telemetry. Account-level monitoring, diagnostics, and operational observations produced within the live product environment where applicable.
Used to support product-state claims, operating-process observations, monitoring outputs, and selected service-layer findings.
Claim Mapping Rule
Every strong public claim should map to one of three foundations:
- source-backed evidence,
- internal methodological output, or
- an explicit status label where the claim is not source-backed.
This rule prevents unsupported public assertions from floating without provenance, methodological grounding, or declared trust status.
Claim Classes and Source Foundations
Company and offer architecture. Typical status: Self-stated or Verified. Source foundation: Official company pages and internal governance records.
Product capabilities and scope. Typical status: Verified or Planned. Source foundation: Product specification and release-state records.
Modeled outcomes and simulation examples. Typical status: Modeled. Source foundation: Internal simulation methodology and scenario datasets.
Market-shift and adoption assertions. Typical status: Verified. Source foundation: Public 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, revise, 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 client businesses.
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.
Operating Status
Source mapping is active and continuously maintained. As Evidentity's public research surface grows, this registry will continue to expand with clearer claim references, stronger provenance links, and more explicit freshness markers across commercial, methodological, and category-level statements.
The objective is not only to publish claims. It is to maintain a public surface that remains legible, reviewable, and trustworthy over time.
Status Note
This page serves as a canonical reference for 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.