identify-issues-in-civil-investigative-demand

name	identify-issues-in-civil-investigative-demand
task_id	antitrust-competition/identify-issues-in-civil-investigative-demand
description	Closes gaps in privilege survival analysis, data preservation and disclosure obligations, oral testimony scheduling, information-exchange assessment, and petition grounds.
activates_for	["planner","solver","checker"]

Skill: CID Issues Memorandum

1. Subject-matter triage

• Treat the CID as both a document demand and a procedural challenge problem: identify what must be produced, what may be withheld, what must be preserved, and what must be scheduled or moved.
• First identify the full set of custodians, repositories, time periods, and specifications implicated by the source set; do not analyze any issue as though it were singular if the documents present multiple categories.
• Where the record points to a filing, objection, petition, or modification request deadline, surface it early and tie every recommended step to that timing.

2. Failure modes the skill is correcting

• Baseline does not distinguish personal communications from business communications; personal exchanges remain outside attorney-client protection even if later routed through counsel.
• Baseline assumes common-interest protection survives automatically; the analysis must test whether a continuing shared legal interest still exists and whether any agreement or surrounding facts alter that result.
• Baseline omits the obligation to analyze preservation gaps, lost data, and whether the government should be told about missing material.
• Baseline under-analyzes oral testimony logistics by failing to flag conflicts, waiver risk, and the need for a prompt modification request.
• Baseline treats CID objections as generic; the memo must separate overbreadth, burden, privilege, procedural defect, and substantive scope objections.
• Baseline misses the antitrust-specific distinction between lawful, aggregated, historical, or anonymized information exchanges and risky current, disaggregated, competitor-identifiable exchanges.
• Baseline may overlook that company control over business records can extend to personal devices or personal accounts used for business purposes.
• Baseline states conclusions without anchoring them to the governing doctrine, rule, or statutory authority.

3. Legal frameworks / domain conventions that apply

• Attorney-client privilege: requires a legal purpose and confidential communication for the purpose of seeking or providing legal advice; personal or social communications are not privileged merely because they were forwarded to counsel.
• Common-interest doctrine: protects communications shared among parties with a shared legal interest in actual or anticipated litigation or another qualifying legal matter; assess whether the common legal interest remains active and whether the doctrine survives any settlement, termination, or change in alignment.
• CID modification or set-aside relief: analyze overbreadth, undue burden, irrelevance, privilege, procedural defects, and noncompliance with statutory or regulatory requirements under the applicable federal civil investigative demand regime.
• Preservation and spoliation principles: once the duty to preserve attaches, a failure to preserve or migrate data may create disclosure and remediation issues; evaluate scope, timing, and feasibility of recovery.
• Antitrust information-exchange principles: evaluate whether the exchange involves current versus historical information, identified competitors versus anonymized aggregates, and direct competitor access versus neutral-third-party compilation.
• Control and possession principles: discovery obligations can reach materials in the company’s possession, custody, or control, including business records on personal devices or accounts used for work.
• Oral testimony obligations: if the CID sets testimony dates, assess conflicts, whether a timely request to reschedule is warranted, and whether inaction risks waiver or default.
• Use the governing authority named in the source set where provided; otherwise cite the controlling federal statute, regulation, or doctrine by name in the analysis.

4. Analytical scaffolds

• Start with an issue map organized by category, then run the same analysis frame for each category and each implicated document set.
• For each issue, identify:
  • the governing rule or authority;
  • the factual trigger in the source documents;
  • the document set, witness set, or data set to which it applies;
  • the practical consequence for the client if the issue is not addressed.
• When multiple custodians, systems, periods, or exchanges appear in the source set, enumerate them explicitly before analyzing them.
• For privilege issues, separate:
  • legal advice communications;
  • business communications;
  • personal communications;
  • joint-defense or common-interest communications;
  • documents shared with third parties or outsiders.
• For data issues, assess:
  • whether data was lost, not migrated, or otherwise inaccessible;
  • when the preservation duty likely arose;
  • what recovery steps are still feasible;
  • whether disclosure to the government is prudent or required.
• For procedural issues, assess:
  • service and compliance defects;
  • burden and timing concerns;
  • oral testimony scheduling conflicts;
  • whether a petition or modification request should be filed and on what theory.
• For substantive scope issues, assess whether the CID seeks information that could evidence unlawful coordination, especially current pricing, competitor-specific outputs, or non-aggregated market data.
• Close each issue with three moves: tie it to a figure, period, or other concrete source-document anchor; cross-reference the interacting document, schedule, or specification; and state the downstream consequence for the client.
• Rank recommendations by strength when multiple theories are available; identify weak but colorable arguments separately from stronger ones.
• Cite the controlling authority for each legal proposition rather than stating conclusions in free-standing form.

5. Vertical / structural / temporal relationships

• Track how the CID specifications relate to one another, especially where one request defines the scope of another or where one category of material overlaps with privilege, preservation, or testimony obligations.
• Track how timing changes the legal analysis: pre-investigation conduct, post-investigation preservation, post-settlement common-interest status, and pre-deadline modification rights can produce different outcomes.
• Track custodian-to-device and business-to-personal-account relationships where company records may sit on individual devices.
• Track source-to-source relationships among the nine documents so that contradictions, updates, and confirmations are not treated as independent facts.
• If a time-sensitive step is implicated, state the practical consequence of waiting, including any waiver, default, or loss-of-relief risk.

6. Output structure conventions

• Write the memo as an advisory issue memorandum for the lead partner.
• Open with an executive summary that prioritizes the highest-risk issues and the most time-sensitive actions.
• Include a clear severity scale at the top of the memo and apply it uniformly to every issue.
• Organize the body by conventional categories such as privilege, preservation/data, procedure/testimony, and substantive scope.
• For each issue entry, include the governing authority, the factual basis from the source set, the practical impact, and the recommended response.
• Include a dedicated section on modification or set-aside options, with grounds ranked by strength and a deadline/timing note.
• Include a dedicated preservation and recovery section if any data gap or migration issue appears in the source documents.
• End with a Recommended Actions section that assigns each action to a role and a timing anchor drawn from the source documents or tied to the nearest regulatory milestone.
• Keep the memo self-contained and readable for partner review; do not use rubric-style headings or disclose internal scoring language.