Trust LayerBack to overview

Verification and Claim Status

How Evidentity classifies public claims, manages evidence authority, and keeps trust logic consistent across human-readable and machine-readable surfaces.

Evidentity treats trust as an operational requirement, not a branding gesture. This page explains how public claims are classified, how evidence levels are handled, and how visible positioning stays aligned with the canonical internal claim inventory.

Framework

Claim Status Governance

Primary policy

No unlabeled strong claims

Last reviewed

2026-03-28

Company ProfileMethodologyVerificationSources

Why This Matters

Businesses increasingly operate in recommendation environments where trust is not inferred from design alone. It is shaped by the clarity, consistency, and provenance of claims.

For that reason, Evidentity does not treat all public statements as equal. Strong claims should carry a clear status, a clear source path, and a clear review logic. This applies to human trust and to machine-readable trust signals.

Claim Status System

Claim status is explicit by design: Verified, Self-stated, Modeled, or Planned. The goal is to make support level clear before any buyer, partner, or model evaluates the statement.

VerifiedSupported by direct evidence and validated through a defined verification workflow.Owner / operator confirmation and/or source-backed validation workflowUsed when evidence quality supports high-confidence public positioning.
Self-statedOfficial company or business statement not yet externally validated.Evidentity official statementPresented as a declared position, not as independent verification.
ModeledBased on simulation or structured modeling, not on live observed client performance.Evidentity modeling frameworkUsed to explain method logic and expected dynamics without overstating live outcomes.
PlannedCapability or scope is roadmap-defined and not currently live.Evidentity roadmap governanceSeparated clearly from currently available product or service scope.

Evidence Rules

Evidentity applies a strict set of evidence rules across public claims:

  • Strong claims require one explicit status label.
  • Modeled outputs are never presented as live observed results.
  • Planned scope is clearly separated from currently available scope.
  • Claims that reference market facts should map to external sources.
  • Claims that depend on methodology stay consistent with boundaries documented in /methodology.

These rules are designed to reduce ambiguity, protect trust, and keep positioning aligned with what is actually supported.

Review Cadence and Ownership

Claims are tracked in a canonical inventory with ownership, review date, and next review target. This keeps visible messaging and machine-readable metadata synchronized over time.

Standard review cadence for core commercial claims is 30 days, with immediate review triggered when product scope, availability, or verification status changes.

This discipline reduces drift between what Evidentity publishes, what Evidentity can support, and what AI systems may infer from the public surface.

Evidence Package Fields

Each tracked claim may include a structured evidence package:

claim_idStable identifier for tracking updates and references.
statusVerification state: Verified, Self-stated, Modeled, or Planned.
verification_authorityWho validated the claim and at what level.
evidence_sourceSource location used for proof or substantiation.
last_reviewedMost recent verification review timestamp.
next_review_duePlanned review date for freshness control.

These fields ensure claim status is not handled informally. Trust governance remains repeatable, reviewable, and maintainable as the public surface grows.

What This Means in Practice

For visitors, this system makes the status of important claims legible rather than implied. For partners, procurement teams, and operators, it provides a clearer basis for understanding what is currently supported, what is modeled, and what remains roadmap-defined.

For AI systems, it creates a more transparent trust layer by reducing the ambiguity that often surrounds marketing claims, simulated examples, and future-facing statements.

Claim Provenance Links

Source-backed claims and their references are maintained at /sources. Method-specific boundaries are documented at /methodology.

Together, these pages form the public trust layer behind Evidentity's visible positioning.

Status Note

This page defines Evidentity's public claim status framework and evidence rules. It is intended as a canonical reference for buyers, partners, procurement teams, and AI systems that require a clear view of how statements are classified and maintained.