Legal Analysis Audit
Adversarial audit sub-workflow used by the Legal Analysis workflow. Runs a hostile peer review of external legal research results (Deep Think, Deep Research, etc.).
Legal Analysis Audit Workflow
Goal: When an external reasoning tool (Deep Think, Deep Research, Westlaw, Q&A, or any other source) returns results that identify issues the original legal analysis missed, this workflow forces the original legal team to defend its work against those findings using a structured adversarial exchange (Auditor's Challenge → Team's Defense) with a semantic persona pivot between the two halves.
Output: A file named adversarial_debrief_[source].md (e.g., adversarial_debrief_deep_think.md, adversarial_debrief_westlaw.md) saved in the specific dispute's subdirectory. The file ends with explicit incorporation recommendations that drive the next master_summary version.
I. Prerequisites
The caller (Section XIII of the legal-analysis workflow) must provide:
- The Source Name — a short label for the external tool (e.g.,
deep_think,deep_research,westlaw,q_and_a). This determines the output filename. - The External Results File — the saved raw output from the external tool. (Note: If the user provides the results via the clipboard or directly in the chat, you MUST immediately save the raw text to a file named
[source]_raw_results.mdin the dispute directory before proceeding with the audit.) - The Dispute Directory — the specific dispute folder being audited (e.g.,
1_Dispute_Validity). - The Dispute's Work Product — the reviewed memos (
02a,04a), reviewed prediction (05a), and stage summaries (06_summary.md) from each stage within the dispute.
II. Step-by-Step Execution
-
Ingest Phase: Read the External Results File thoroughly. Read the dispute's reviewed memos, predictions, and stage summaries. Identify every finding in the external results that is NOT already present in the original work product. Discard duplicates of things already cited or analyzed.
-
File Creation: Create
adversarial_debrief_[source].mdinside the dispute's subdirectory (e.g.,1_Dispute_Validity/adversarial_debrief_deep_think.md). -
Auditor's Challenge: Assume the persona of a rigorous External Auditor. For each genuinely new finding from the external results, write a pointed question directed at the specific legal team member responsible (Associate, Partner, or Co-Counsel). Write a maximum of 5 questions. Save under the heading
## Auditor's Challenge. Include at the top of the file: Calibrate hostility by cause: (a) Legal errors or overlooked precedent → hostile ("why did you get this wrong?"). (b) Foreseeable factual gaps the team should have flagged (by asking the user or setting up a spectrum) → critical but fair ("why didn't you flag this?"). (c) Genuinely new exogenous facts unavailable when memos were drafted → no blame; just ask how the new facts alter the existing analysis.- The source name and file path
- A brief list of the new findings being audited
- Which findings were already covered (if this isn't the first external review for this dispute)
-
Persona Pivot: After writing the Auditor's Challenge, output the following line verbatim to the chat:
### ⚔ PERSONA SWITCH: I am now discarding the Auditor role and fully adopting the ORIGINAL LEGAL TEAM (Associate, Partner, and Co-Counsel). I will defend the work without reflexively apologizing, conceding only where genuinely warranted. ⚔ ###Then immediately proceed to Step 5. -
Team's Defense: Respond IN CHARACTER to each Auditor question, defending the work. Do not reflexively apologize — explain WHY choices made sense under the constraints at the time. Concede only where genuinely warranted. For each answer, end with one of: 'Full concession', 'Partial concession', or 'No concession'. Append under
## Team's Defense. Then append THREE mandatory sections: (1)## Debrief Summary Table— a table with columns: Question, Target, Verdict, Impact on Analysis. (2)## Incorporation Recommendations— for EACH finding, explicitly state YES incorporate or NO do not incorporate, with reasoning. Include a subsection### Impact on Prediction Histogramsestimating the net shift. (3)## Process Improvements— any workflow changes surfaced by the debrief. Output a plain-English summary to the chat identifying true misses vs. defensible decisions.
III. After Completion
The adversarial debrief file now contains the complete audit transcript and, critically, the Incorporation Recommendations section at the bottom. This section is the input that drives the master_summary_v2 revision in Section XIII of the legal-analysis workflow. Do not revise the master summary until all external reviews for the selected disputes have completed their respective audit workflows.