open-agreements 0.7.5 → 0.7.6

package/content/templates/openagreements-due-diligence-request-list/README.md

@@ -0,0 +1,68 @@
+# OpenAgreements Legal Due Diligence Request List
+
+A modular legal due-diligence request list (DDRL) for corporate transactions.
+Free to use under CC BY 4.0.
+
+## Structure
+
+The template ships a base form covering the core categories that appear in
+90%+ of public-source DDRLs (corporate organization, capitalization,
+subsidiaries, financial/tax, debt, material contracts, property, IP,
+privacy/cybersecurity, employment, litigation, compliance, insurance,
+related-party). Four optional industry riders gate via boolean toggles in
+`metadata.yaml`:
+
+| Section | Rider | Toggle field | When to enable |
+|---------|-------|--------------|----------------|
+| O | Tech / SaaS | `tech_rider_enabled` | Software, SaaS, marketplace, or data-heavy targets |
+| P | Life Sciences | `life_sciences_rider_enabled` | Biotech, pharma, medtech, diagnostics targets with FDA-regulated pipelines |
+| Q | Healthcare Provider | `healthcare_provider_rider_enabled` | Clinics, hospitals, physician groups, telehealth providers with payer-reimbursement exposure |
+| R | Cross-Border / Trade Compliance | `cross_border_rider_enabled` | Foreign subsidiaries, foreign customers, government customers, controlled-jurisdiction exposure |
+
+Each rider is rendered in `template.docx` inside its own `{IF rider_enabled}…{END-IF}` sub-table so the docx-templates "one IF per row" constraint is honored.
+
+## AI augmentation
+
+Each rider has a paired `additional_questions_<rider>` array field. AI
+workflows (or human drafters) populate these arrays with target-specific
+custom questions; the DOCX renders them via `{FOR q IN <array>}` loops at
+the end of the matching section. A separate `additional_questions_general`
+array covers cross-cutting questions that don't belong to any rider.
+
+The arrays are independent because the OA validator's `SAFE_TAG_RE` forbids
+inline filtering of a shared array (see `validation/template.ts:252`). When
+a future renderer extension lifts that constraint, the arrays can be merged
+into a single shared array filtered by section.
+
+## Materiality and lookback
+
+The cover sheet specifies a global dollar threshold (`materiality_threshold_usd`,
+default `$100,000`), a relative-revenue threshold
+(`materiality_threshold_revenue_pct`, default `5%`), and a default lookback
+(`lookback_years`, default `3`). Three optional override fields
+(`litigation_lookback_years`, `tax_lookback_years`, `compliance_lookback_years`)
+let drafters extend specific sections without changing the global default.
+
+The dollar-threshold fields are stored as pre-formatted strings (e.g.,
+`"$100,000"`) because the OA fill engine has no currency formatter. When a
+formatter is added, these can become `type: number`.
+
+## Sources and attribution
+
+The category structure is drawn from public-source consensus across 15 Am
+Law firm, bar association, and legal publisher DDRLs (Cooley, Skadden,
+Morgan Lewis, Gunderson Dettmer, Lowenstein Sandler, Holland & Knight,
+Foley & Lardner, Software Equity Group, the International Bar Association,
+the American Bar Association, Bass Berry & Sims, and Carta). All language
+is original; no source language was reused.
+
+## Files
+
+- `metadata.yaml` — field definitions and template metadata.
+- `template.docx` — fillable Word document with `{field}` placeholders and `{IF}` rider gates.
+- `template.md` — flat human-readable mirror of the document body.
+- `README.md` — this file.
+
+## License
+
+CC BY 4.0. Attribute "OpenAgreements contributors."

package/content/templates/openagreements-due-diligence-request-list/metadata.yaml

@@ -0,0 +1,300 @@
+name: OpenAgreements Legal Due Diligence Request List
+category: deals-partnerships
+description: >-
+  Modular legal due diligence request list (DDRL) for corporate transactions.
+  Ships a base form covering organization, capitalization, contracts, IP,
+  employment, litigation, compliance, tax, insurance, debt, property, and
+  privacy/cybersecurity. Four optional industry riders gate via boolean
+  toggles: tech / SaaS, life sciences, healthcare provider, and cross-border
+  / trade compliance. Drafted clean-room from public-source consensus across
+  15 Am Law firm, bar association, and legal publisher DDRLs; no public
+  source language is reused. Includes per-section AI-augmentable arrays so
+  AI workflows can append target-specific custom questions to any rider.
+source_url: https://github.com/open-agreements/open-agreements/tree/main/content/templates/openagreements-due-diligence-request-list
+version: '1.0'
+license: CC-BY-4.0
+allow_derivatives: true
+attribution_text: >-
+  Authored by OpenAgreements contributors. Category structure and consensus
+  framing informed by publicly available DDRLs and commentary from Cooley,
+  Skadden, Morgan Lewis, Gunderson Dettmer, Lowenstein Sandler, Holland &
+  Knight, Foley & Lardner, Software Equity Group, the International Bar
+  Association, the American Bar Association, Bass Berry & Sims, and Carta.
+  See practice note for sources. Drafted clean-room; no source language was
+  reused. Licensed under CC BY 4.0.
+
+priority_fields:
+  - target_company_name
+  - requesting_firm_name
+  - deal_type
+  - transaction_stage
+  - tech_rider_enabled
+  - life_sciences_rider_enabled
+  - healthcare_provider_rider_enabled
+  - cross_border_rider_enabled
+  - materiality_threshold_usd
+  - lookback_years
+
+fields:
+  # --- Cover Sheet (always rendered) ---
+  - name: requesting_firm_name
+    type: string
+    description: Legal name of the buyer's law firm sending the request
+    section: Cover Sheet
+  - name: target_company_name
+    type: string
+    description: Legal name of the target company receiving the request
+    section: Cover Sheet
+  - name: project_code_name
+    type: string
+    description: Project code name or pseudonym used to refer to the transaction
+    default: ''
+    section: Cover Sheet
+  - name: request_date
+    type: date
+    description: Date the request list is delivered to the target
+    section: Cover Sheet
+  - name: response_due_date
+    type: date
+    description: Date by which the target's first-round response is due
+    section: Cover Sheet
+  - name: lead_buyer_counsel_name
+    type: string
+    description: Name of the lead attorney at the requesting firm
+    section: Cover Sheet
+  - name: lead_buyer_counsel_email
+    type: string
+    description: Email of the lead attorney at the requesting firm
+    section: Cover Sheet
+  - name: primary_target_contact_name
+    type: string
+    description: Name of the target's primary point of contact for diligence responses
+    section: Cover Sheet
+  - name: currency
+    type: enum
+    description: Currency for materiality and financial threshold inputs
+    options:
+      - USD
+      - EUR
+      - GBP
+      - CAD
+      - Other
+    default: USD
+    section: Cover Sheet
+  - name: data_room_url
+    type: string
+    description: URL of the virtual data room (optional; included in cover-sheet instructions if provided)
+    default: ''
+    section: Cover Sheet
+
+  # --- Materiality and Lookback ---
+  - name: materiality_threshold_usd
+    type: string
+    description: >-
+      Dollar floor for material-contracts requests. Stored as a pre-formatted
+      string (e.g., "$100,000") because the fill engine has no currency
+      formatter. Adjust upward for larger deals, downward for early-stage
+      targets.
+    default: '$100,000'
+    default_value_rationale: >-
+      $100,000 is the consensus dollar floor for mid-market deals across
+      public DDRLs (Cooley, Skadden, Bloomberg). Tune up for larger targets
+      (e.g., "$1,000,000" for $100M+ deals) or down for early-stage.
+    section: Materiality and Lookback
+  - name: materiality_threshold_revenue_pct
+    type: string
+    description: >-
+      Relative materiality threshold expressed as a percentage of gross
+      revenue. The lower of dollar floor and revenue percentage governs.
+      Stored as a pre-formatted string for consistency with the dollar
+      threshold.
+    default: '5%'
+    default_value_rationale: >-
+      5% of gross revenue is the consensus relative-materiality qualifier
+      in BigLaw practice. Tune down for asset-light targets where individual
+      contract size is small but each one is operationally critical.
+    section: Materiality and Lookback
+  - name: lookback_years
+    type: number
+    description: >-
+      Default lookback window in years for litigation, compliance, and
+      operational history. Per-category overrides may extend specific
+      sections.
+    default: '3'
+    default_value_rationale: >-
+      3 years is consensus baseline for litigation, compliance, and
+      operational history. Tax often warrants 6+ to mirror IRS statute of
+      limitations; regulatory correspondence is conventionally open-ended.
+    section: Materiality and Lookback
+  - name: litigation_lookback_years
+    type: number
+    description: >-
+      Optional per-category override for the litigation lookback window.
+      If blank, falls through to lookback_years. 5 years is appropriate for
+      regulated targets or where prior litigation revealed systemic process
+      failures.
+    default: ''
+    section: Materiality and Lookback
+  - name: tax_lookback_years
+    type: number
+    description: >-
+      Optional per-category override for the tax lookback window. If blank,
+      falls through to lookback_years. 6 years mirrors the IRS substantial-
+      omission statute of limitations and is the safe default for most deals.
+    default: ''
+    section: Materiality and Lookback
+  - name: compliance_lookback_years
+    type: number
+    description: >-
+      Optional per-category override for routine compliance certifications.
+      Regulatory correspondence regarding investigations, settlements, and
+      consent decrees should be requested open-ended regardless of this value.
+    default: ''
+    section: Materiality and Lookback
+
+  # --- Deal Type ---
+  - name: deal_type
+    type: enum
+    description: Type of transaction the DDRL supports
+    options:
+      - private_ma_stock_purchase
+      - private_ma_asset_purchase
+      - venture_financing
+      - private_equity_buyout
+      - ipo_preparation
+      - public_ma
+      - cross_border_ma
+    section: Deal Type
+  - name: transaction_stage
+    type: enum
+    description: >-
+      Stage of the transaction. Pre-LOI uses lighter scope; post-LOI uses
+      the full base form plus all triggered riders.
+    options:
+      - pre_loi
+      - post_loi_pre_signing
+      - signing_to_closing
+      - post_closing_review
+    default: post_loi_pre_signing
+    section: Deal Type
+
+  # --- Industry Riders (boolean toggles; each gates a {IF}…{END-IF} sub-table in the DOCX) ---
+  - name: tech_rider_enabled
+    type: boolean
+    description: >-
+      Enable Section O (Tech / SaaS rider) covering OSS schedules with
+      copyleft flagging, source-code escrow, hosted-services agreements,
+      SOC 2 / ISO 27001 audits, data-flow architecture, SLAs, security-
+      incident history, and cloud-agreement change-of-control. Recommended
+      on for software, SaaS, platform, marketplace, or data-heavy targets.
+    default: 'false'
+    section: Industry Riders
+  - name: life_sciences_rider_enabled
+    type: boolean
+    description: >-
+      Enable Section P (Life Sciences rider) covering FDA correspondence,
+      clinical trials, CRO agreements, Form 483s, Warning Letters, CIA,
+      and controlled-substance registrations. Recommended on for biotech,
+      pharma, medical-device, and diagnostics targets with FDA-regulated
+      pipelines.
+    default: 'false'
+    section: Industry Riders
+  - name: healthcare_provider_rider_enabled
+    type: boolean
+    description: >-
+      Enable Section Q (Healthcare Provider rider) covering HIPAA breach
+      logs, billing/coding compliance, payer audits, malpractice claims,
+      and Anti-Kickback / Stark / Sunshine Act compliance. Recommended on
+      for clinics, hospitals, physician groups, and telehealth providers
+      with payer-reimbursement exposure.
+    default: 'false'
+    section: Industry Riders
+  - name: cross_border_rider_enabled
+    type: boolean
+    description: >-
+      Enable Section R (Cross-Border / Trade Compliance rider) covering
+      sanctions/OFAC screening, export-control classifications, AML/KYC,
+      FCPA compliance, government-customer exposure, and foreign-investment-
+      screening filings. Recommended on whenever the target has foreign
+      subsidiaries, foreign customers, government customers, or sensitive-
+      jurisdiction exposure. Increasingly mandatory after the 2023 DOJ
+      M&A Safe Harbor Policy.
+    default: 'false'
+    section: Industry Riders
+
+  # --- Cross-border specifics (rendered inside Section R when cross_border_rider_enabled) ---
+  - name: countries_of_operation
+    type: string
+    description: >-
+      Comma-separated list of countries where the target operates, sells,
+      or has employees. Optional; populated when the cross-border rider is
+      enabled to focus the request on specific jurisdictions.
+    default: ''
+    section: Cross-Border Specifics
+  # --- AI-augmentable per-rider question arrays ---
+  # Each array holds {question: string} items. The DOCX uses
+  # {FOR q IN <array>}{$q.question}{END-FOR q} loops at the end of the
+  # matching section to render any AI-generated or human-authored
+  # target-specific additions. Arrays are independent per rider because
+  # the validator's SAFE_TAG_RE forbids inline filtering of a single
+  # shared array (see plan Track D follow-up).
+  - name: additional_questions_tech
+    type: array
+    description: >-
+      AI-augmentable list of target-specific custom questions appended to
+      the Tech / SaaS rider. Each item is an object with a `question` field.
+      Empty by default. Renders only when tech_rider_enabled is true.
+    default: '[]'
+    section: AI Augmentation
+    items:
+      - name: question
+        type: string
+        description: The custom question text to render in Section O
+  - name: additional_questions_life_sciences
+    type: array
+    description: >-
+      AI-augmentable list of target-specific custom questions appended to
+      the Life Sciences rider. Empty by default. Renders only when
+      life_sciences_rider_enabled is true.
+    default: '[]'
+    section: AI Augmentation
+    items:
+      - name: question
+        type: string
+        description: The custom question text to render in Section P
+  - name: additional_questions_healthcare_provider
+    type: array
+    description: >-
+      AI-augmentable list of target-specific custom questions appended to
+      the Healthcare Provider rider. Empty by default. Renders only when
+      healthcare_provider_rider_enabled is true.
+    default: '[]'
+    section: AI Augmentation
+    items:
+      - name: question
+        type: string
+        description: The custom question text to render in Section Q
+  - name: additional_questions_cross_border
+    type: array
+    description: >-
+      AI-augmentable list of target-specific custom questions appended to
+      the Cross-Border / Trade Compliance rider. Empty by default. Renders
+      only when cross_border_rider_enabled is true.
+    default: '[]'
+    section: AI Augmentation
+    items:
+      - name: question
+        type: string
+        description: The custom question text to render in Section R
+  - name: additional_questions_general
+    type: array
+    description: >-
+      AI-augmentable list of cross-cutting custom questions that do not
+      belong to any specific rider. Renders at the end of the closing
+      Response Protocol section. Empty by default.
+    default: '[]'
+    section: AI Augmentation
+    items:
+      - name: question
+        type: string
+        description: The custom question text to render at end of document