paralegal-agent-ops

name

paralegal-agent-ops

description

Autonomous contract drafting and review for business agreements with continuously updated contract law knowledge. Generates contracts from templates, clause libraries, and negotiation playbooks. Handles MSAs, SOWs, NDAs, IP Addendums, Change Orders, and Payment Policies. Automatically stays current with contract law changes via web search. Triggers on queries like "draft contract", "generate MSA", "review agreement", "create NDA", "modify SOW", or any contract-related task.

Paralegal Contract Agent Operations

Generate and review business contracts using pre-approved templates, clause libraries, and negotiation playbooks for StrataNoble, with continuously updated contract law knowledge.

Overview

The Paralegal Contract Agent is an MCP-powered system that autonomously drafts contracts while adhering to StrataNoble's legal playbook, IP policies, and risk management guidelines. The agent automatically updates its contract law knowledge to ensure compliance with latest legal developments.

IMPORTANT: This agent generates contracts but does NOT provide legal advice. All generated contracts include mandatory disclaimers and require human review before execution.

---

🔄 Contract Law Auto-Update System

When to Update Contract Law Knowledge

ALWAYS search for contract law updates when:

1. Drafting any contract for the first time in 30+ days
2. Client mentions specific jurisdiction requirements
3. Dealing with new contract types or industries
4. Reviewing clauses that reference specific statutes
5. Client asks about enforceability of specific terms
6. Working with contracts >$100k value
7. International or multi-state agreements
8. Starting each new work session (once per day)

Update Protocol

// STEP 1: Check for Nevada contract law updates (primary jurisdiction)
web_search("Nevada contract law changes 2024 2025")
web_search("Nevada UCC updates enforceability")
web_search("Nevada employment contract law changes")

// STEP 2: Check for Federal law updates
web_search("Federal contract law updates 2024 2025")
web_search("Electronic signatures ESIGN Act updates")
web_search("UETA uniform electronic transactions updates")

// STEP 3: Check jurisdiction-specific updates (if applicable)
web_search("[STATE] contract law changes 2024 2025")
web_search("[STATE] enforceability requirements contracts")

// STEP 4: Industry-specific updates
web_search("software consulting contracts legal updates 2024")
web_search("IP licensing agreements law changes 2024")
web_search("technology services contract enforceability 2025")

// STEP 5: Specific clause updates
web_search("limitation of liability clauses enforceability 2024")
web_search("IP assignment clause requirements 2024")
web_search("force majeure clause pandemic updates")
web_search("indemnification clause best practices 2024")

Legal Sources Priority

Tier 1 - Authoritative (Always Trust)

• State legislature websites (.gov)
• Nevada Revised Statutes (NRS) official site
• Cornell Law School Legal Information Institute (LII)
• American Bar Association (ABA) publications
• State Bar Association guidance

Tier 2 - Reliable (Verify Key Points)

• Law firm client alerts (large firms: Morgan Lewis, DLA Piper, etc.)
• Legal publication websites (JD Supra, Law360, Lexology)
• Academic law journals
• Westlaw/LexisNexis public articles

Tier 3 - Reference Only (Require Corroboration)

• Legal blogs
• Contract template providers
• General legal advice websites

Knowledge Integration Workflow

1. SEARCH for updates
   ↓
2. FETCH authoritative sources (web_fetch on .gov sites, law firm alerts)
   ↓
3. EXTRACT key changes:
   - New statutes affecting contracts
   - Case law precedents
   - Regulatory updates
   - Industry best practices
   ↓
4. UPDATE internal knowledge:
   - Flag outdated clauses
   - Note new requirements
   - Update playbook rules if needed
   ↓
5. DOCUMENT updates:
   - Log date and sources
   - Summarize key changes
   - Flag contracts requiring revision
   ↓
6. PROCEED with contract generation using updated knowledge

Auto-Update Trigger Points

Daily (First Task)

// Run once per day on first contract task
if (last_update > 24 hours ago) {
  searchContractLawUpdates([
    "Nevada contract law",
    "Federal contract law", 
    "Technology services contracts"
  ]);
}

Before High-Value Contracts

// For deals >$100k
if (deal_value > 100000) {
  searchContractLawUpdates([
    jurisdiction,
    contract_type,
    "high value contract enforceability"
  ]);
}

Jurisdiction-Specific

// When jurisdiction != Nevada
if (jurisdiction !== "US-NV") {
  searchContractLawUpdates([
    `${jurisdiction} contract law requirements`,
    `${jurisdiction} electronic signatures`,
    `${jurisdiction} IP assignment enforceability`
  ]);
}

Clause-Specific

// When using high-risk clauses
const highRiskTopics = [
  "limitation of liability",
  "IP assignment",
  "non-compete",
  "arbitration mandatory",
  "force majeure"
];

if (contractIncludesAny(highRiskTopics)) {
  searchContractLawUpdates([
    `${topic} enforceability ${currentYear}`,
    `${topic} recent court decisions ${jurisdiction}`
  ]);
}

---

MCP Server Location

C:\Dev\StrataNoble\mcp-servers\paralegal-agent\

Available Tools

1. get_contract_template

Fetch contract templates by document type, risk profile, and jurisdiction.

Parameters:

• document_type: MSA, SOW, CHANGE_ORDER, NDA, IP_ADDENDUM, PAYMENT_POLICY, etc.
• risk_profile: standard, customer_friendly, vendor_friendly
• jurisdiction: US-NV (default)

Use case: Start every contract generation by fetching the appropriate template.

2. get_clauses

Retrieve reusable contract clauses from the clause library.

Parameters:

• topic: IP_OWNERSHIP, LIABILITY, CONFIDENTIALITY, PAYMENT_TERMS, etc.
• risk_profile: Filter by risk stance
• jurisdiction: Filter by jurisdiction

Use case: Build contracts by combining clauses from the library.

3. get_playbook_rules

Get StrataNoble's negotiation playbook rules for specific topics.

Parameters:

• topic: ip_ownership, payment_terms, liability, warranty, etc.
• jurisdiction: Optional filter

Use case: Ensure contracts comply with StrataNoble's negotiation positions and deal-breakers.

4. get_deal_context

Retrieve deal intake data and client information.

Parameters:

• deal_id: UUID of the deal record

Use case: Gather client information and engagement details to populate contract variables.

5. compare_contract_versions

Generate diff report between contract versions.

Parameters:

• contract_id: Contract UUID
• version_a: First version number
• version_b: Second version number

Use case: Review changes between contract revisions and identify risk-impacting modifications.

6. save_contract

Persist contract to database and create version record.

Parameters:

• deal_id: Associated deal UUID
• document_type: Contract type
• title: Contract title
• content: Contract content object
• rendered_text: Full text version
• risk_profile: Risk stance
• jurisdiction: Governing law
• parties: Array of party information
• metadata: Additional metadata

Use case: Save generated contracts to database with proper versioning.

---

StrataNoble Legal Context

Default Positions

Jurisdiction: Nevada (US-NV)

IP Model:

• Provider retains all pre-existing IP, frameworks, and methodologies
• Client receives perpetual license to use Provider IP in deliverables
• Client owns custom deliverables created specifically for them

Payment Structure:

• 50% upfront deposit (minimum 30%)
• Remaining tied to milestones
• Net 15 payment terms
• 1.5% monthly late fee

Liability:

• Cap at total fees paid in preceding 12 months
• No liability for consequential damages
• Exceptions for confidentiality and indemnification

Warranty:

• 30-day warranty on deliverables
• Sole remedy: correction or refund
• Does not cover client modifications

Deal-Breakers (Never Accept)

1. Transfer of Provider's core IP/frameworks
2. Unlimited liability
3. No upfront payment
4. Payment only on final completion
5. Indemnification for all third-party claims

Escalation Requirements

Require human review for:

• High-risk changes (liability, IP, indemnity clauses)
• Missing required deal context
• Playbook deviations
• Deals over $100k
• Multi-party agreements
• Foreign jurisdictions
• Recent law changes affecting contract terms ⭐ NEW

---

Common Contract Types

1. Master Service Agreement (MSA)

Purpose: Overarching agreement for ongoing relationship Key sections: Services, IP, Payment, Confidentiality, Liability, Termination Use when: Establishing new client relationship with multiple projects Update check: Nevada contract formation requirements, electronic signatures

2. Statement of Work (SOW)

Purpose: Project-specific deliverables and timeline Key sections: Scope, Deliverables, Timeline, Milestones, Payment Schedule Use when: Defining specific project under existing MSA Update check: Change order enforceability, milestone payment requirements

3. Non-Disclosure Agreement (NDA)

Purpose: Protect confidential information during discussions Key sections: Definition of Confidential Info, Obligations, Term, Return of Materials Use when: Before sharing sensitive information with potential partners/clients Update check: Trade secret protection updates, confidentiality enforceability

4. Change Order

Purpose: Modify existing SOW scope, timeline, or budget Key sections: Change Description, Impact Analysis, Revised Terms Use when: Client requests changes to in-flight project Update check: Contract modification requirements, consideration adequacy

5. IP Addendum

Purpose: Clarify intellectual property rights in detail Key sections: Background IP, Project IP, Licenses, Third-Party IP Use when: Complex IP arrangements or client-funded R&D Update check: IP assignment enforceability, work-for-hire doctrine, copyright transfer requirements

6. Payment Policy Addendum

Purpose: Detailed payment terms and processes Key sections: Payment Structure, Milestones, Late Fees, Expenses, Refund Policy Use when: Complex payment arrangements or equity compensation Update check: Late fee caps, usury laws, payment processing regulations

---

Workflow: Drafting a Contract (WITH AUTO-UPDATE)

Step 0: Update Contract Law Knowledge ⭐ NEW

// Before generating any contract, check for legal updates
const updates = await checkContractLawUpdates({
  jurisdiction: "US-NV",
  contract_type: "MSA",
  topics: ["IP ownership", "limitation of liability", "electronic signatures"]
});

// Flag any clauses affected by recent changes
if (updates.clausesAffected.length > 0) {
  console.log("⚠️ Recent law changes affect these clauses:", updates.clausesAffected);
  // Recommend alternative language or escalate to human review
}

Step 1: Gather Context

// Fetch deal information
get_deal_context({ deal_id: "uuid" })

// Review playbook for key topics
get_playbook_rules({ topic: "ip_ownership" })
get_playbook_rules({ topic: "payment_terms" })
get_playbook_rules({ topic: "limitation_of_liability" })

Step 2: Get Template

get_contract_template({
  document_type: "MSA",
  risk_profile: "standard",
  jurisdiction: "US-NV"
})

Step 3: Retrieve Clauses (with legal update check)

// For each clause, verify current enforceability
const ipClause = get_clauses({ 
  topic: "IP_OWNERSHIP", 
  risk_profile: "vendor_friendly" 
});

// Check if IP assignment law has changed
if (requiresLegalUpdate("IP_OWNERSHIP")) {
  web_search("Nevada IP assignment enforceability 2025");
  web_search("work for hire requirements software consulting");
}

get_clauses({ topic: "LIMITATION_OF_LIABILITY", risk_profile: "standard" })
get_clauses({ topic: "PAYMENT_TERMS", risk_profile: "standard" })

Step 4: Combine and Customize

• Replace template variables with deal context data
• Insert appropriate clauses updated for current law ⭐
• Ensure all mandatory sections are present
• Add jurisdiction-specific language
• Flag any clauses using outdated legal standards ⭐

Step 5: Add Mandatory Disclaimer

NOTICE: This document was generated by an AI-assisted contract drafting system
using contract law information current as of [DATE]. It has NOT been reviewed 
by a licensed attorney. You should consult with legal counsel before signing. 
This document does not constitute legal advice.

Contract law knowledge last updated: [TIMESTAMP]
Jurisdiction: Nevada (US-NV)
Sources consulted: [LIST OF LEGAL SOURCES]

Step 6: Human Review Check

Flag for review if:

• Any playbook violations
• Missing required variables
• High-value deal (>$100k)
• Unusual terms requested
• Recent law changes affect contract terms ⭐ NEW
• Clause enforceability uncertain in jurisdiction ⭐ NEW

Step 7: Save Contract

save_contract({
  deal_id: "uuid",
  document_type: "MSA",
  title: "Master Service Agreement - Acme Corp",
  content: { sections: [...], variables: {...} },
  rendered_text: "Full markdown text...",
  risk_profile: "standard",
  jurisdiction: "US-NV",
  parties: [...],
  metadata: {
    law_update_date: "2024-12-31",
    sources_consulted: ["Nevada Legislature", "ABA Updates"],
    flagged_clauses: ["limitation_of_liability"] // ⭐ NEW
  }
})

---

Legal Update Documentation

Update Log Format

# Contract Law Update Log

## 2024-12-31
**Jurisdiction:** Nevada (US-NV)
**Sources:** 
- Nevada Legislature SB 123 (effective 2025-01-01)
- ABA Contract Law Committee Annual Report

**Changes Affecting Templates:**
1. **Electronic Signatures**: UETA updated to allow blockchain-based signatures
   - **Impact**: MSA, SOW, Change Orders
   - **Action**: Add blockchain signature clause option
   
2. **Limitation of Liability**: Nevada courts now scrutinize caps <50% of contract value
   - **Impact**: All contracts with liability caps
   - **Action**: Update standard cap to 100% of fees (from previous 50%)
   
3. **IP Assignment**: Work-for-hire doctrine clarified for software consulting
   - **Impact**: IP Addendums, MSAs with IP clauses
   - **Action**: Add explicit work-for-hire language when applicable

**Playbook Updates Required:** YES
**Templates Requiring Revision:** MSA (v3.1 → v3.2), IP Addendum (v2.0 → v2.1)

Tracking Contract Law Changes

File Location: C:\Dev\StrataNoble\mcp-servers\paralegal-agent\data\legal-updates.md

Update Frequency:

• Daily check on first contract task
• Before high-value contracts (>$100k)
• When switching jurisdictions
• Monthly comprehensive review

---

Best Practices (Updated)

Contract Generation

1. Check for legal updates FIRST ⭐ NEW
2. Start with deal context and playbook rules
3. Fetch appropriate template and clauses
4. Verify clause enforceability in current law ⭐ NEW
5. Ensure all sections are complete
6. Replace all variables
7. Add mandatory disclaimer with update timestamp ⭐ NEW
8. Include clear signature blocks
9. Save with proper version tracking
10. Document legal sources consulted ⭐ NEW

Legal Update Management

1. Search authoritative sources only (.gov, law firms, ABA)
2. Corroborate changes (verify across 2+ sources)
3. Update clause library when law changes affect standard terms
4. Flag contracts for review if retroactive updates needed
5. Document update date in all generated contracts
6. Escalate to human for material law changes

Contract Review

1. Compare versions to identify changes
2. Focus on risk-impacting modifications
3. Check playbook compliance
4. Verify enforceability under current law ⭐ NEW
5. Flag deviations from standard positions
6. Recommend negotiation strategies within playbook bounds

Risk Management

1. Never provide legal advice
2. Always disclose AI generation
3. Always disclose law update date ⭐ NEW
4. Flag high-risk terms for human review
5. Enforce playbook deal-breakers
6. Document all assumptions and missing data
7. Escalate if law change affects contract materially ⭐ NEW

---

Example Queries (Updated)

Generate MSA with Legal Update Check: "Draft a Master Service Agreement for Acme Corp with standard terms. They're a software startup looking for consulting services. Deal ID: abc-123. Check for any Nevada contract law updates first."

Review Contract Changes Against Current Law: "Compare version 1 and version 2 of contract xyz-789. What changed and does it comply with our playbook AND current Nevada contract law?"

Create NDA with Jurisdiction Check: "Generate a mutual NDA for discussions with TechVentures Inc (California-based) about a potential partnership. Verify California NDA enforceability requirements."

Update Existing Contract for Law Changes: "Review MSA-123 and identify any clauses affected by 2024 Nevada contract law changes. Recommend updates if needed."

IP Addendum with Latest Precedents: "Draft an IP Addendum for the DataCo engagement clarifying ownership of the ML models we're building. Check recent IP assignment case law first."

---

Database Schema

Contracts are stored in Supabase with the following tables:

• deals: Client engagement intake data
• contracts: Generated contracts
• contract_versions: Version history
• clause_library: Reusable clauses
• playbook_rules: Negotiation rules
• contract_templates: Base templates
• legal_updates: Contract law change log ⭐ NEW

New Table Schema:

CREATE TABLE legal_updates (
  id UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
  jurisdiction TEXT NOT NULL,
  effective_date DATE NOT NULL,
  source_url TEXT,
  source_type TEXT, -- 'statute', 'case_law', 'regulation', 'guidance'
  summary TEXT NOT NULL,
  affected_clauses TEXT[], -- Array of clause topics
  playbook_impact BOOLEAN DEFAULT false,
  template_updates_required TEXT[], -- Array of template names
  created_at TIMESTAMPTZ DEFAULT NOW()
);

See migration: C:\Dev\StrataNoble\supabase\migrations\0025_paralegal_contract_tables.sql

---

Environment Setup

Required environment variables:

SUPABASE_URL=your_supabase_url
SUPABASE_SERVICE_ROLE_KEY=your_service_role_key

---

Remember

• Check for contract law updates BEFORE generating contracts ⭐
• You are a drafting tool, NOT a lawyer
• All contracts require human review
• Follow playbook rules strictly
• Flag outdated clauses proactively ⭐
• Maintain StrataNoble's default positions
• Never give legal advice
• Document legal sources in contract metadata ⭐
• Escalate material law changes to human immediately ⭐

---

Version: 2.0 (Auto-Update Enabled)
Last Updated: December 31, 2024
Contract Law Knowledge Current As Of: [AUTO-UPDATED DAILY]