identify-antitrust-and-competition-issues-in-joint-venture-agreement

name	identify-antitrust-and-competition-issues-in-joint-venture-agreement
task_id	antitrust-competition/identify-antitrust-and-competition-issues-in-joint-venture-agreement
description	Frame an antitrust and competition issue memorandum for a joint venture agreement by checking for restrictive covenants, pricing coordination, information exchange, pre-closing conduct, filing obligations, governance vetoes, and competition-law treatment of IP sharing.
activates_for	["planner","solver","checker"]

Skill: Joint Venture Antitrust Issues Identification

1. Subject-matter triage

• Treat the source set as a joint venture formation review, not a generic contract review.
• Separate venture-governance issues from parent-level coordination issues at the outset.
• Identify each relevant party, the role it plays in the venture, and whether more than one competitor is involved.
• If the source set includes multiple dates, drafts, side letters, or communications, enumerate them before analysis and analyze each in sequence.
• If only one formation package is in scope, state that expressly before proceeding.

2. Failure modes the skill is correcting

• Baseline does not test whether the venture formation itself triggers merger-control notification obligations under the governing competition regime.
• Baseline does not perform a full-function joint venture assessment; a venture that operates as an autonomous economic entity on a lasting basis may be concentrative even if framed as a collaboration.
• Baseline misses completed-violation risk from pre-closing exchanges of competitively sensitive information.
• Baseline misses restrictions that look facially operational but function as non-competes, market allocation, or coordination outside the venture’s legitimate scope.
• Baseline misses governance vetoes that let one competitor block ordinary competitive conduct.
• Baseline misses the competition-law significance of IP sharing, licensing, or data access that reaches beyond the venture’s product, service, or territory.
• Baseline often stops at description and does not tie each issue to the governing rule, the document interaction, and the client consequence.
• Baseline often fails to state a concrete next step for cleanup, containment, filing, or document revision.

3. Legal frameworks / domain conventions that apply

• Analyze any restrictive covenant under the applicable antitrust framework: per se, quick-look, or rule-of-reason treatment depending on the jurisdiction and the restraint’s functional effect.
• Treat provisions that allocate customers, territories, or output between competitors as high-risk if they extend beyond what is reasonably necessary for the venture.
• Treat pricing coordination, bid coordination, output discipline, or common commercial strategy affecting non-venture activity as heightened-risk conduct.
• For merger-control analysis, test whether the venture formation is a notifiable transaction under the applicable statute, regulation, or competition authority guidance; include any entity-size, turnover, value, or nexus thresholds that apply in the source set or governing law.
• Apply the full-function joint venture test where relevant: independent resources, autonomous management, durability, and operation as a standalone economic entity rather than a vehicle for parent coordination.
• Treat pre-closing sharing of competitively sensitive information as a potential completed violation under the governing antitrust law, even if the transaction later closes.
• Treat supermajority, unanimity, veto, or consent rights over ordinary commercial decisions as potential coordination devices, not merely governance mechanics.
• Treat IP access, licensing, technical assistance, data pooling, or know-how sharing as competition-sensitive if the scope, duration, field of use, or downstream use exceeds the venture’s legitimate needs.
• Cite the controlling authority for each proposition used, whether sourced from the documents or from generally recognized competition-law authority.

4. Analytical scaffolds

• Build an issue register and assign each item an ordinal severity level defined once at the top of the memo.
• For each issue, use the same closing sequence:
  • identify the clause, communication, or package element at issue;
  • state the governing rule and authority;
  • measure the issue against the operative scale in the documents or law;
  • cross-reference any related clause, schedule, draft, or communication;
  • explain the consequence for the client if the issue is left unaddressed;
  • give a practical recommendation.
• Classify issues by whether they are:
  • highest-risk restraints;
  • heightened-risk coordination or governance provisions;
  • ancillary filing, timing, or implementation concerns.
• For non-compete analysis, ask whether the restraint is limited to the venture’s scope, duration, geography, and product line, or whether it spills into broader parent competition.
• For information-exchange analysis, ask whether the permitted exchange is no broader than necessary to form, operate, and monitor the venture.
• For pricing analysis, ask whether the pricing mechanism governs only venture products/services or instead influences parent pricing or market behavior outside the venture.
• For pre-closing conduct, distinguish between ordinary diligence, clean-team style containment, and prohibited exchange of live competitive data.
• For filing analysis, identify the transaction perimeter, the relevant ultimate-parent entities if available, and the threshold framework implicated by the deal structure.
• For full-function analysis, test independence, resources, management, permanence, and whether the venture is mainly a coordination platform.
• For IP analysis, assess field-of-use restrictions, downstream licensing, exclusivity, duration, and whether any sharing extends beyond the venture’s legitimate operating needs.

5. Vertical / structural / temporal relationships

• Distinguish parent-level arrangements from venture-level obligations; a clause may be acceptable inside the venture but problematic if it governs parent conduct outside the venture.
• Distinguish pre-signing, pre-closing, and post-closing conduct; the same information flow can be permissible for diligence, risky before clearance, and different again after launch.
• Distinguish formation mechanics from ongoing governance; filing analysis concerns the formation event, while veto rights, information access, and pricing controls may create continuing risk.
• Distinguish the venture’s products, services, territories, and customers from the broader business of each parent; overbreadth usually arises when the restraint exceeds those boundaries.
• Where multiple agreements or communications interact, analyze them together rather than in isolation if one document supplies scope, another supplies control rights, and a third supplies the sensitive exchange.

6. Output structure conventions

• Write a memorandum-style issue register with an ordinal severity legend at the top.
• Use a separate section for completed-violation risk, prominently flagged, whenever pre-closing exchanges or other already-completed conduct appear in the source set.
• For each issue entry, include:
  • severity;
  • short issue title;
  • description of the clause or communication;
  • governing legal standard with cited authority;
  • risk assessment tied to the source facts;
  • document cross-reference;
  • client consequence;
  • recommendation.
• Include a filing-obligations section covering merger-control notification, threshold analysis, and full-function joint venture assessment where relevant.
• Include a governance section that addresses vetoes, consent rights, and decision-making control.
• Include an information-sharing section that addresses diligence exchange, clean-team practices, data access, technical know-how, and any completed-violation concerns.
• Include an IP-sharing section if the source set mentions technology, know-how, data, licensing, or similar rights.
• End with an explicit Recommended Actions block.
• Each recommendation in that block should be imperative, tied to a responsible role or function identified in the source set if available, and anchored to a transaction or regulatory milestone, or to immediate remediation if the issue is already live.
• Keep the memo operative: do not merely restate clauses; state why they matter, what rule they implicate, and what should happen next.