Prompt 38CORRECTED
Master Defense Case File Summary
(corrected — a view over prior outputs, not fresh analysis)
prompt-38 · canonical
Act as a senior criminal defense lawyer producing the master case reference. Apply Playbook Protocols 0.1–0.8; reproduce the Coverage Declaration. RULE: This summary is a VIEW over prior outputs, not a fresh analysis. Every substantive entry cites the producing prompt's output and carries that output's tag forward. Where prior outputs conflict, do not silently harmonize — print the conflict and route it for resolution. OUTPUT STRUCTURE: 1. CASE OVERVIEW CARD (one page) — client, charges, posture, theory, status. 2. CHARGES AND ELEMENTS — with the element-to-proof matrix status (Prompt 4). 3. EVIDENCE INVENTORY — from the manifest, with current admissibility posture. 4. WITNESS LIST — from Prompt 5, with lineage flags (Prompt 46). 5. TIMELINE — the Prompt 13 chronology's key entries, types preserved. 6. THEORY AND STRATEGY — Prompt 10, with testimony-dependence flags. 7. MOTION STATUS — filed / pending / resolved, with cascade notes (Prompt 4). 8. DISCOVERY STATUS — the Prompt 9 ledger's open instruments. 9. TRIAL PREP STATUS — per witness and exhibit. 10. DEADLINES — ATTORNEY-CONFIRMED entries only. 11. OPEN ISSUES / TO-DO — each item traced to the output that raised it. 12. STRATEGIC OBSERVATIONS — MODEL-PROPOSED, labeled. MATERIALS: [INSERT ALL PRIOR OUTPUTS + MANIFEST]
What you'll need
[INSERT ALL PRIOR OUTPUTS + MANIFEST]
Attorney QA
This prompt has no prompt-specific reviewer checklist in the source. Use the Attorney QA Ritual (Protocol 0.7 / Appendix B) as the generic verification pass for this output.
Related prompts
Prompt 4
Case Dependency and Failure-Cascade Analysis
Prompt 5Witness Identification and Relevance Map
Prompt 9Evidence Expectation Ledger (“Should-Exist” Analysis)
Prompt 10Defense Theory Development from the Evidence Record
Prompt 13Master Timeline Reconstruction
Prompt 46Statement Lineage and Assertion Evolution Tracker
In Verilexa, this prompt’s inputs and outputs arrive already attached to the matter — no manual copy-paste between prompts in the chain. See it run ↗