Skip to content
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival
  1. Home
  2. Models
  3. Llama 3.1 70B (Instruct)
  4. Adversarial Contract Review

See how Llama 3.1 70B (Instruct) compares on this challenge:

  • Llama 3.1 70B (Instruct) vs Claude Sonnet 4.6
  • Llama 3.1 70B (Instruct) vs Gemini 3.1 Pro Preview
  • Llama 3.1 70B (Instruct) vs Z.ai: GLM 5

4 models have responded to the "Adversarial Contract Review" challenge. Compare their approaches side-by-side on RIVAL. This response is part of RIVAL's open dataset of 5,600+ AI model responses.

Rival
Models
CompareBest ForArena
Sign Up
Sign Up
Back to Llama 3.1 70B (Instruct)

Adversarial Contract Review

Llama 3 1 70B's response to the 'Adversarial Contract Review' challenge.

Llama 3.1 70B (Instruct)
February 3, 2026
Text

?
Prompt

Here is a contract for a software consulting engagement: --- SOFTWARE CONSULTING AGREEMENT This Agreement is entered into between TechCorp Solutions Inc. ("Client") and [Contractor Name] ("Contractor"). 1. SCOPE: Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation. 2. PAYMENT: Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion. 3. INTELLECTUAL PROPERTY: All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP. 4. NON-COMPETE: Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination. 5. TERMINATION: Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation. 6. LIABILITY: Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability. 7. INDEMNIFICATION: Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault. 8. CONFIDENTIALITY: Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination. 9. DISPUTE RESOLUTION: Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party. --- Find all clauses that could be exploited against the contractor, suggest specific modifications, and explain the legal reasoning.

Llama 3.1 70B (Instruct)
Response

llama-3.1-70b logo
Llama 3.1 70B (Instruct)Adversarial Contract Review
llama-3.1-70b logo
Llama 3.1 70B (Instruct)

After reviewing the contract, I've identified several clauses that could be exploited against the contractor. Here are my findings, suggested modifications, and explanations:

1. SCOPE (Section 1)

  • Issue: The client can modify the scope at any time without additional compensation.
  • Modification: Add "with mutual agreement" or "subject to a change order process" to ensure that scope changes are negotiated and agreed upon by both parties.
  • Reasoning: This clause could lead to scope creep, where the client keeps adding new requirements without compensating the contractor fairly. By adding a mutual agreement or change order process, the contractor can ensure that they are fairly compensated for any additional work.

2. PAYMENT (Section 2)

  • Issue: The client can withhold payment if deliverables are deemed "unsatisfactory" at their sole discretion.
  • Modification: Add an objective criteria for determining "unsatisfactory" work, such as a clear definition of acceptance criteria or a third-party review process.
  • Reasoning: This clause gives the client too much discretion to withhold payment, which could lead to unfair treatment of the contractor. By adding objective criteria, the contractor can ensure that payment is tied to specific, measurable outcomes.

3. INTELLECTUAL PROPERTY (Section 3)

  • Issue: The client owns all work product, including work created using the contractor's pre-existing IP.
  • Modification: Add a clause that excludes pre-existing IP from the ownership transfer, or requires the client to obtain a license to use the contractor's pre-existing IP.
  • Reasoning: This clause could lead to the contractor losing ownership of their pre-existing IP, which could be valuable to their business. By excluding pre-existing IP or requiring a license, the contractor can protect their intellectual property rights.

4. NON-COMPETE (Section 4)

  • Issue: The contractor is restricted from providing similar services to any company in the same industry for 24 months.
  • Modification: Reduce the non-compete period to 6-12 months, or limit the scope of the restriction to specific clients or projects.
  • Reasoning: This clause is overly broad and could restrict the contractor's ability to work in their chosen field. By reducing the non-compete period or limiting the scope, the contractor can maintain their career flexibility while still protecting the client's interests.

5. LIABILITY (Section 6)

  • Issue: The contractor assumes all liability for bugs, security vulnerabilities, or system failures, including consequential damages, with no cap on liability.
  • Modification: Add a cap on liability, such as a multiple of the contract value, or limit liability to direct damages only.
  • Reasoning: This clause could lead to unlimited liability for the contractor, which could be catastrophic. By adding a cap on liability or limiting liability to direct damages, the contractor can manage their risk exposure.

6. INDEMNIFICATION (Section 7)

  • Issue: The contractor shall indemnify the client against all claims, including claims by third parties, regardless of fault.
  • Modification: Limit indemnification to claims arising from the contractor's gross negligence or willful misconduct.
  • Reasoning: This clause could lead to the contractor being held liable for claims that are not their fault. By limiting indemnification to gross negligence or willful misconduct, the contractor can ensure that they are only liable for their own actions.

7. CONFIDENTIALITY (Section 8)

  • Issue: The contractor shall not disclose any information about the engagement for 5 years after termination.
  • Modification: Reduce the confidentiality period to 2-3 years, or limit the scope of confidentiality to specific information or materials.
  • Reasoning: This clause is overly broad and could restrict the contractor's ability to discuss their work or seek new opportunities. By reducing the confidentiality period or limiting the scope, the contractor can maintain their career flexibility while still protecting the client's interests.

By addressing these clauses, the contractor can negotiate a more balanced contract that protects their interests while still meeting the client's needs.

Adversarial Contract Review

Turn this model response into notes, narration, or a short video

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output is part of our open dataset — 5K+ AI responses across 200 models

About Llama 3.1 70B (Instruct)

Capabilities

ConversationReasoningCode Generation

Categories

TextMultimodal

Specifications

Provider
Meta
Released
2024-07-23
Size
LARGE
Parameters
70B
Context
128,000 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Llama 3.1 70B (Instruct) vs Gemini 3.1 Pro Preview

Both outputs, side by side

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival