Evidence folder page
Evidence Examples
Examples of what earns credit, what stays neutral, and what becomes hidden trust when claims outrun public evidence.
Strong Evidence
✓ Strong evidenceStrong
Fresh-clone setup, deterministic validation commands, CI, decision history, and current docs/thc provenance tied to the reviewed commit.
✓ Strong hardeningStrong
Tests or checks are named, runnable, documented, and connected to CI or an equivalent repeatable validation path.
Partial / Needs Improvement
△ Partial evidenceImprove
A useful README or architecture note exists, but validation commands, freshness, or operational handoff are incomplete.
△ Needs improvementImprove
Evidence exists but is scattered, stale, inconsistent, or requires guessing across unrelated files.
△ Stale evidenceImprove
Local artifacts or docs reference a different revision than the reviewed public commit.
Missing / No Public Credit
× Missing evidenceAbsent
Claims of reliability, safety, or production readiness appear without inspectable public files.
× Private evidenceAbsent
Maintainer knowledge, private dashboards, private tests, or closed docs. Useful internally, but not public score evidence.
× Hidden trustAbsent
Any place the reader must trust reputation or vibes because public evidence does not close the loop.