---
name: project-evidence-ledger
description: Use when adding, updating, or reviewing evidence records or evidence indexes. Ensures EV-* records support completion claims, validations, decisions, document promotions, memory updates, health findings, and traceability entries.
---

# Project Evidence Ledger

Use this skill to keep evidence queryable and source-backed.

Boundary vs `project-evidence`: use `project-evidence` to **create** a single
evidence record (a validation run, red-green output, a reviewed artifact); use
this skill to **index/review** the `EV-*` ledger — confirm each record is valid,
complete, and linked into traceability.

## Evidence Entry

Each `EV-*` entry should include:

1. ID.
2. Date.
3. Claim.
4. Supported IDs.
5. Source artifacts.
6. Commands, checks, or reviewed artifacts.
7. Result.
8. Limitations.
9. Regression condition when relevant.
10. Linked `HLT-*` health finding when evidence resolves a health issue.
11. `AGENT-*` and `SES-*` provenance when evidence supports promoted memory or
    tracking state.

## Rules

- Use individual files under `docs/evidence/` for formal evidence records.
- Use `prd_find`/`prd_get` to review the ledger and `prd_link` to connect
  supported records. Create evidence through `prd_record_evidence`; its ID and
  registry update are atomic.
- Stored binary evidence is valid and remains inspectable as an artifact; only
  supported textual claim sources are decoded for canonical-ID analysis.
- Use `.prd_plugin/state/health.json` to close health findings that evidence resolves.
- Link evidence from traceability maps when it supports a mapped requirement or decision.
- Do not use changelog entries as substitutes for evidence records.
- Do not let evidence text claim `MEM-*`, `TRK-*`, `CHG-*`, `OBS-*`, or
  `SES-*` updates that are absent from canonical PRD Plugin state.
- Run the required downstream validator
  `python scripts/state_consistency_check.py --repo-root .` after evidence
  ledger changes that mention memory, tracking, changelog, session summaries,
  registry counters, or timestamped fixtures.

## Staleness Coverage

Apply the shared policy in `.prd_plugin/method/staleness-rules.md`.


When evidence resolves or refreshes a stale record, link the stale `REQ-*`,
`TRK-*`, `DBR-*`, `MEM-*`, or `HLT-*` ID and record the current verification
date, limitations, and regression condition. Evidence indexes should make stale
refreshes queryable.

## Completion Claims

A completion claim should cite at least one `EV-*` record. If evidence is
missing, create it before claiming completion. If evidence claims durable state
updates, verify those state records exist before claiming completion.