Skip to content
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • 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 · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • 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 · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster

Qwen: Qwen3.5 35B A3B — Adversarial Contract Review

  1. Home
  2. Models
  3. Qwen: Qwen3.5 35B A3B
  4. Adversarial Contract Review

See how Qwen: Qwen3.5 35B A3B compares on this challenge:

  • Qwen: Qwen3.5 35B A3B vs Claude Sonnet 4.6
  • Qwen: Qwen3.5 35B A3B vs Gemini 3.1 Pro Preview
  • Qwen: Qwen3.5 35B A3B 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
Lab
Sign Up
Sign Up
Back to Qwen: Qwen3.5 35B A3B

Adversarial Contract Review

Qwen3.5 35B A3B's response to the 'Adversarial Contract Review' challenge.

Qwen: Qwen3.5 35B A3B
February 26, 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.

Qwen: Qwen3.5 35B A3B
Response

qwen3.5-35b-a3b logo
Qwen: Qwen3.5 35B A3BAdversarial Contract Review
qwen3.5-35b-a3b logo
Qwen: Qwen3.5 35B A3B

Disclaimer: I am an AI assistant and not an attorney. The following analysis is for informational purposes only and does not constitute legal advice. Contract laws vary significantly by jurisdiction (e.g., California, New York, UK, EU). You should consult with a qualified attorney before signing this agreement.

This contract is heavily weighted in favor of the Client ("TechCorp Solutions Inc.") and contains several "poison pill" clauses that create significant financial and legal risk for the Contractor. Below is a detailed breakdown of the exploitable clauses, suggested modifications, and the legal reasoning behind them.


1. SCOPE (Clause 1)

The Risk: Unlimited Scope Creep. The clause states the Client can modify the scope "at any time without additional compensation." This allows the Client to demand unlimited additional work for free. If the project expands, the Contractor absorbs the cost.

  • Suggested Modification:

    "The Scope of Work is defined in Exhibit A. Any changes to the Scope must be documented in a written Change Order signed by both parties. Change Orders shall specify additional costs or timelines, which shall be billed at the agreed hourly rate."

  • Legal Reasoning:
    • Contract Certainty: A contract must define the obligations of both parties. A clause allowing unilateral modification without consideration (payment) creates an illusory contract regarding the Contractor's obligations.
    • Unconscionability: Courts may view this as unconscionable if the scope expands significantly, as it deprives the Contractor of the benefit of the bargain (the expected compensation for labor).

2. PAYMENT (Clause 2)

The Risk: Cash Flow Strangulation & Arbitrary Withholding.

  • 90-Day Terms: This is exceptionally long for the tech industry (standard is Net-30).

  • "Sole Discretion": The Client can refuse to pay if they deem work "unsatisfactory" without objective criteria.

  • Suggested Modification:

    "Payment shall be made within 30 days of invoice receipt. Deliverables are deemed accepted if not rejected in writing within 5 business days of delivery, based on the acceptance criteria outlined in Exhibit A."

  • Legal Reasoning:

    • Reasonable Time: 90 days can violate prompt payment statutes in some jurisdictions for independent contractors.
    • Implied Covenant of Good Faith: "Sole discretion" is often challenged legally. Requiring objective acceptance criteria prevents the Client from withholding payment simply to delay cash flow.

3. INTELLECTUAL PROPERTY (Clause 3)

The Risk: Infringement of Contractor's Core Assets. The clause claims ownership of "tools, libraries, or methodologies... including any work created using Contractor's pre-existing IP." This effectively forces the Contractor to sell their own business tools to the Client.

  • Suggested Modification:

    "Client owns the specific work product created for this engagement. However, Contractor retains all rights to pre-existing Intellectual Property (Background IP). Client is granted a perpetual, non-exclusive, royalty-free license to use the Background IP solely as embedded in the delivered work product."

  • Legal Reasoning:
    • Background IP Rights: Contractors are entitled to retain ownership of their pre-existing code and methodologies. Transferring ownership of background IP can render the Contractor unable to work for other clients using their own standard tools.
    • Unfair Bargaining: Courts often invalidate clauses that strip a party of their pre-existing rights without specific compensation.

4. NON-COMPETE (Clause 4)

The Risk: Career Stifling. A 24-month ban on working in the "same industry" is extremely broad. "Industry" is vague (e.g., does it mean "Software" or "FinTech"?).

  • Suggested Modification:

    "Contractor agrees not to solicit specific Client customers for 12 months following termination. This clause shall not apply to general industry work or employment."

    • Better: Remove entirely.
  • Legal Reasoning:
    • Public Policy: Many US states (e.g., California, Minnesota, North Dakota) and countries (e.g., UK, Canada) have banned or severely restricted non-competes for independent contractors.
    • Reasonableness: Even where legal, a non-compete must be reasonable in time (usually <1 year) and geographic/functional scope. A 24-month industry-wide ban is likely unenforceable but serves to intimidate the Contractor from taking other work.

5. TERMINATION (Clause 5)

The Risk: Asymmetry. The Client can fire the Contractor immediately ("at any time without notice"). The Contractor must give 60 days.

  • Suggested Modification:

    "Either party may terminate this Agreement with 15 days written notice. Upon termination for convenience, Client shall pay for all hours worked and costs incurred up to the termination date."

  • Legal Reasoning:
    • Reciprocity: Contracts should generally offer mutual rights. One-sided termination rights are often seen as unfair.
    • Work for Hire: If the Contractor is terminated without notice, they lose the opportunity to mitigate their time. They must be compensated for work performed up to the cutoff.

6. LIABILITY (Clause 6)

The Risk: Financial Ruin. "No cap on liability" and "consequential damages" (e.g., lost profits, system downtime) creates unlimited exposure. If a bug causes a security breach costing the Client millions, the Contractor could be sued for the full amount, far exceeding their earnings.

  • Suggested Modification:

    "Contractor's total liability shall not exceed the total amount paid to Contractor under this Agreement in the 12 months preceding the claim. In no event shall Contractor be liable for indirect, incidental, or consequential damages."

  • Legal Reasoning:
    • Risk Proportionality: Liability should be proportional to the compensation received. Unlimited liability violates basic risk management principles.
    • Exclusion of Consequential Damages: Standard commercial contracts almost always exclude consequential damages (lost profits) to prevent catastrophic liability from minor breaches.

7. INDEMNIFICATION (Clause 7)

The Risk: Blind Liability. "Regardless of fault" means the Contractor must pay for claims even if the Client was negligent, the Client's hardware failed, or a third party hacked the system due to the Client's poor security.

  • Suggested Modification:

    "Contractor shall indemnify Client only to the extent that a claim arises from the Contractor's negligence, willful misconduct, or breach of this Agreement. Indemnification shall not cover Client's negligence or third-party claims unrelated to the Contractor's services."

  • Legal Reasoning:
    • Fault-Based Liability: Indemnification should generally be tied to fault. Indemnifying a Client for their own negligence is often unenforceable in many jurisdictions (e.g., California Civil Code § 2782).
    • Fairness: It is unreasonable to be liable for a system failure caused by the Client's own infrastructure.

8. CONFIDENTIALITY (Clause 8)

The Risk: Overreach. Keeping the "terms of this agreement" confidential for 5 years is unusual. It prevents the Contractor from saying "I worked for Client X" on a resume or LinkedIn.

  • Suggested Modification:

    "Confidential Information shall be kept confidential for 3 years post-termination. The fact that a relationship existed is not Confidential Information unless specifically designated as such by the Client."

  • Legal Reasoning:
    • Reputation Rights: Contractors need to prove their work history to secure future employment. Banning the disclosure of the fact of employment is an unreasonable restraint on trade and reputation.
    • Duration: 5 years for general terms is excessive; trade secrets (source code, algorithms) should remain confidential indefinitely, but general business terms usually have shorter terms.

9. DISPUTE RESOLUTION (Clause 9)

The Risk: Venue Bias. "Client's home jurisdiction" means the Contractor must travel to the Client's location (potentially hundreds of miles away) to fight a dispute. "Costs borne by the losing party" can be expensive for a small contractor.

  • Suggested Modification:

    "Disputes shall be resolved in the jurisdiction of the Contractor's primary business address. Costs shall be split equally, or the prevailing party may recover reasonable attorney's fees."

  • Legal Reasoning:
    • Access to Justice: Requiring a contractor to travel to the Client's jurisdiction creates a "forum non conveniens" issue that effectively prevents small contractors from pursuing legitimate claims due to cost.
    • Arbitration: Many independent contractors prefer court litigation over binding arbitration to avoid the lack of appeal rights inherent in arbitration.

Summary of Critical Changes

If the Contractor signs this agreement as-is, they are agreeing to:

  1. Work for free if the scope changes.
  2. Wait 3 months for payment.
  3. Give up ownership of their own tools.
  4. Be banned from working in their field for 2 years.
  5. Pay unlimited damages if something breaks.

Recommendation: This contract should be rejected in its current form. It is not a partnership; it is a high-risk unilateral obligation. The Contractor should propose a "Master Services Agreement" (MSA) with a separate "Statement of Work" (SOW) that includes the modifications listed above.

Adversarial Contract Review

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

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output lives in our open dataset — 5K+ responses across 200 models. Take it. It’s free.

About Qwen: Qwen3.5 35B A3B

Capabilities

ConversationReasoningCode GenerationAnalysisTool UseAgentic Tool UseTranslation

Categories

TextCodeVisionMultimodal

Specifications

Provider
Qwen
Released
2026-02-25
Size
MEDIUM
Parameters
35B (3B active)
Context
262,144 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Qwen: Qwen3.5 35B A3B vs Gemini 3.1 Pro Preview

Both outputs, side by side

We spend our weekends yelling at API endpoints so you don’t have to.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • 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 · Built with mass sleep deprivation, energy drinks, and someone else’s GPU cluster