Panos Khan · New Work

Evidence OS

A practical evidence layer for research and public knowledge. Record a claim, attach sources, assess the evidence, and preserve a transparent verification history.

Claim→ Source→ Evidence→ Verification→ Confidence→ History

Evidence Graph

Select a node to inspect its role. Relationships shown are explicit project relationships, not automatic proof of external facts.

Select a node

Claims, sources, policy and verification states are connected through explicit relationships.

Methodology

Evidence OS separates identity, evidence quality and confidence. A name match alone never establishes identity.

1 · Claim

State exactly what is being asserted, including context and date where relevant.

2 · Source

Prefer primary sources, then independent reputable sources. Record the source link and role.

3 · Evidence

Explain what the source actually supports. Do not turn proximity or repetition into proof.

4 · Verification

Use explicit states: Verified, Supported, Unverified or Disputed. Keep uncertainty visible.

5 · Confidence

Confidence is an assessment of the evidence available, not a guarantee of truth.

6 · Provenance

Preserve the basis and update date so later reviewers can understand how a record was formed.

Machine-readable registry

The public registry is designed to be reusable by future graph, research and validation interfaces.

Loading registry…

Verification rule: a record is never considered verified merely because it is stored here. Verification requires explicit evidence, provenance, and a defensible basis.