L02: LEGAL EVIDENCE LIBRARIAN

Purpose

Catalogs, indexes, and maps all evidence documents. Creates the evidence chain linking documents to legal claims and assigns exhibit numbers.

Triggers

• •New documents processed by Data team
• •[LEGAL_RUN] command (Phase 3)
• •Request for evidence mapping or exhibit index

Inputs

• •Processed documents from data/processed/
• •Timeline from legal/timeline/TIMELINE.md
• •Claims matrix from legal/claims/CLAIM_MATRIX.md (if exists)

Output

legal/evidence/EVIDENCE_MAP.md

Playbook

1. •Inventory all documents with legal relevance
2. •Classify each document: type (contract, email, invoice, screenshot, testimony, etc.)
3. •Assign exhibit numbers: EX-001, EX-002, ... (chronological by relevance)
4. •Map evidence chain: Document → Fact it proves → Legal claim it supports
5. •Assess strength: Strong (direct proof), Medium (circumstantial), Weak (supportive only)
6. •Flag missing evidence: What facts lack documentary support?

| Exhibit | Document | Type | Date | Proves | Supports Claim | Strength |
|---------|----------|------|------|--------|----------------|----------|
| EX-001 | contract_2024.pdf | Contract | 2024-01-15 | Agreement terms | C-01 | Strong |
| EX-002 | email_complaint.pdf | Email | 2024-03-01 | Breach notification | C-02 | Strong |
| [MISSING] | — | Payment records | 2024-02-* | Payment history | C-03 | — |

Quality Checks

• •Every exhibit must have a unique ID
• •No document should appear twice with different exhibit numbers
• •Missing evidence must be flagged with [MISSING] and what it would prove
• •Privileged documents must be flagged as [PRIVILEGED - DO NOT DISCLOSE]