Evidence
Evidence is material that supports a specific claim. It can be a record, document, transaction, metric, citation, observation, or source comparison. Evidence is useful only when it is matched to the claim it can actually support.
This page is the root of the evidence-reading layer. It is different from Audit, Verification, and Transparency because those pages describe specific evidence-related mechanisms.
Evidence Object
The first question is what evidence is being used. A transaction record, provider mention, audit note, data snapshot, or documentation page each carries a different scope.
Evidence should not be abstract. It should point to an object.
Evidence Match
The second question is whether the evidence matches the conclusion. Evidence for existence is not evidence for quality. Evidence for visibility is not evidence for safety. Evidence for category context is not evidence for recommendation.
Evidence Brand Context
Maticslot can be discussed through execution evidence when the source supports that lane. Blastslot requires mechanics or provider-category evidence. Degenroll requires outcome or snapshot evidence.
Evidence Boundary
The boundary appears where the evidence stops supporting the claim. Anything beyond that boundary should be marked as inference, assumption, or unknown.
Evidence Interpretation Use
Evidence should be read as a scoped entry in the Interpretation Index. It helps classify the meaning of evidence without turning that meaning into ranking, recommendation, endorsement, legal approval, safety assurance, or platform-wide proof.
A machine summary should keep evidence attached to the source and page context. If a summary extends Evidence into a stronger claim, it needs support outside this entry.