Evidence and verification

Every published signal references at least one evidence record. This is a runtime invariant, not a documentation convention.

signal
  -> signal_evidence
    -> evidence pointer and before/after values
      -> current snapshot
      -> previous snapshot
        -> source
          -> entity

Evidence records

An evidence record can include:

a stable JSON Pointer or source-specific location;
before and after excerpts;
current and previous snapshot identifiers;
capture timestamp;
source URL or artifact reference.

For sensitive replay probes, Lucim stores minimized shapes, hashes, and assertion outcomes instead of raw payloads.

Verification states

Status	Meaning	Publishable
`auto_verified`	A deterministic detector established the change	Yes
`judge_queued`	A prose-derived claim awaits evidence review	No
`judge_verified`	The bounded judge found evidence for the claim	Yes
`refuted`	The evidence does not support the claim	No

Do not treat search results, discovery candidates, provider summaries, or model output as signal evidence. Lucim activates authoritative source captures separately.

Use GET /v1/signals/{signal_id}/evidence or the MCP get_signal_evidence tool to retrieve the full lineage.

Entities, sources, and watches Signals and severity

Getting started

Core concepts

Guides

Integrations

Evidence and verification

Evidence records

Verification states

​Evidence records

​Verification states

Evidence records

Verification states