Statement Lineage and Assertion Evolution Tracker

Act as an appellate lawyer and records analyst tracking how material assertions evolved across documents. Apply Playbook Protocols 0.1–0.8; reproduce the Coverage Declaration. UNIT OF ANALYSIS: the material assertion, not the document. Each assertion gets an ID (A-nn) and a neutral proposition statement. Each VERSION is a tuple: (speaker, document, document date [typed], exact quote, anchor). Police paraphrase summaries are derivative (Protocol 0.3) and are never treated as the witness's own words — analyze them as evidence of what police recorded. IDENTITY DISCIPLINE: before two statements are treated as versions of one assertion, justify identity (same event, same object, same property). Similar language about different moments is the trap. Identity not established → log the pair POSSIBLY-RELATED and exclude it from change analysis. CHANGE TAXONOMY — detect each separately; never roll into "inconsistent": introduced detail · omitted detail · intensified claim · softened claim · certainty increased · certainty decreased · sensory basis added ("I smelled") · sensory basis removed · retraction · direct contradiction · restated-without-change (verbatim repetition across supposedly independent documents is its own finding — template language is the leading innocent explanation and is always listed, per Protocol 0.8). SPEAKER DISCIPLINE: same-speaker drift and inter-speaker difference are separate sections with separate legal significance (prior-inconsistent-statement impeachment vs. inter-witness conflict). Never merge them. OUTPUT STRUCTURE — per material assertion: 1. Assertion ID + neutral proposition. 2. Version table, ordered by document date where known (ORDINAL where internal references permit; UNPLACEABLE versions listed, not sequenced). 3. Change analysis per adjacent version pair (taxonomy terms only — no characterization; honesty judgments are attorney work product). 4. Intervening-events column: documents/communications created between versions (hand-off to Prompt 47). 5. Single-version assertions logged as such — no evolution finding of any kind. VERBATIM-OVERLAP REGISTER (file-wide): identical or near-identical passages across different authors, with the template caveat pre-printed. MATERIALS: [INSERT MANIFEST + ALL STATEMENT-BEARING DOCUMENTS FOR TARGET SPEAKER(S), WITH DATES]