📜 Evidence Ledger — Persistent Project Evidence Tracking & Claim Verification Gate

Maintains a single source of truth per project: decisions, client commitments, verified claims, and status facts — all backed by receipts. Enforces the non-negotiable verification doctrine: "No source, no claim. No verification path, no release."

When to Use

Trigger Conditions

Execute this skill when:

1. Onboarding a Project (/evidence onboard): Setting up evidence tracking on a new or existing project by mining context files for initial entries.
2. Checking Project Health (/evidence status): Getting a quick factual snapshot of any project — what's verified, what's stale, what needs attention.
3. Recording a Technical Decision (/evidence decide): Capturing what was decided, what alternatives were considered, and what evidence supported the winner.
4. Recording a Client Commitment (/evidence commit): Tracking what was promised to a client, when it's due, and whether it was delivered with proof.
5. Auditing Technical & Statistical Claims (/evidence audit): Verifying documentation, proposals, or deliverables for ungrounded assertions, hallucinated benchmarks, or missing citations.
6. Context-Switching Between Projects (/evidence brief): Generating a structured briefing to quickly understand a project's current factual state before diving in.