EVIDENCE · RESEARCH CREDIBILITY

Don't take Loom's word for it.

Loom's central rule is simple: AI can help propose a claim, but the evidence must establish what can responsibly be said. The source, the excerpt, the claim, the checks, and the decision must remain distinguishable.

Important distinction: Loom has written specifications, schemas, and validation code. That does not mean every provenance, audit, or verification safeguard is already implemented and validated on every research artifact.

01

THE EVIDENCE CHAIN

From source to public statement.

01Source

An identifiable document, record, dataset, or other material that can be retrieved and inspected.

02Evidence

A located excerpt or data point, linked to the source and its exact location.

03Observation

A preliminary interpretation that may suggest what to investigate next.

04Claim

A bounded statement whose wording and scope can be assessed against supporting and contradictory evidence.

05Review + decision

Verification and human governance determine whether, and how, a claim may enter the public record.

02

WHAT CHECKS MEAN

A label is only as strong as the work behind it.

Keep these distinctions visible

  • Finding a URL is not retrieving a source.
  • A source containing a passage is not the same as a claim being independently corroborated.
  • Primary-source status does not automatically mean independence.
  • A validator passing structural rules does not prove a claim true.
  • A hash can help identify a captured object; it cannot prove the object is truthful or authentic by itself.
  • An observation is not a claim, and a claim is not a causal diagnosis.

How Loom treats uncertainty

Supporting evidence and contradictory evidence belong in the same research record. Where the record is incomplete, conflicting, or unavailable, the status should say so. “Not found in the searched records” must not quietly become “does not exist.”

Promotion is a governance decision, not an automatic reward for passing a validator. AI cannot promote its own output.

03

READ THE RULES

The full research documents are available here.

04

IMPLEMENTATION STATUS

Specification is not proof of enforcement.

The evidence model is a working specification and implementation target. The repository contains schemas and validator code, but each stronger claim about retrieval, hash verification, independent review, append-only history, or adversarial testing must be supported by actual test results and artifact records. The Flint case is currently undergoing that source-and-provenance audit rather than being represented as a completed reproducible package.