Skip to content

Advanced Commands

FundAdmin AI's advanced commands handle complex multi-document workflows, programmable logic simulation, natural language interaction, and document amendment drafting. These commands are designed for power users and sophisticated fund administration scenarios.


/fund multi-doc-analyze

Description: Performs cross-reference analysis across multiple fund documents simultaneously. Identifies conflicts between documents, traces amendment lineage, detects MFN cascade effects, and builds a unified view of the fund's complete legal framework. Essential when a fund's terms are spread across an LPA, multiple amendments, and dozens of side letters.

Usage

bash
/fund multi-doc-analyze <file1> <file2> [file3] [file4] ...

Inputs

ParameterTypeRequiredDescription
file1File pathYesFirst document (PDF, DOCX, or TXT)
file2File pathYesSecond document (PDF, DOCX, or TXT)
file3...File pathsNoAdditional documents (no practical limit)

Output

Generates MULTI-DOC-ANALYSIS-[fund-name]-[date].md containing:

  • Document Inventory -- list of all documents analyzed with type classification (LPA, amendment, side letter, PPM, subscription), date, and parties
  • Cross-Reference Map -- provisions in each document that reference, modify, or supersede provisions in other documents, with section-level linkage
  • Conflict Detection -- provisions across documents that contradict each other, with severity classification:
    • DIRECT CONFLICT -- mutually exclusive terms (e.g., different management fee rates)
    • AMBIGUITY -- provisions that could be interpreted inconsistently
    • IMPLICIT OVERRIDE -- later document silently changes earlier terms
    • GAP -- expected provision missing from the document set
  • Amendment Lineage -- chronological trace of how each key provision has been modified across documents, showing original language, each amendment, and current effective language
  • MFN Cascade Analysis -- how side letter terms interact when MFN elections are considered, potential chain reactions, and aggregate exposure
  • Unified Terms Summary -- single consolidated view of all effective terms after accounting for amendments, side letters, and superseding provisions
  • Defined Term Reconciliation -- defined terms that appear in multiple documents with different definitions, and the controlling definition based on document hierarchy
  • Priority of Documents -- the established hierarchy of documents (typically: side letter > amendment > LPA > PPM) with analysis of any unclear priority provisions

Example

bash
/fund multi-doc-analyze lpa-original.pdf amendment-1.pdf amendment-2.pdf side-letter-a.pdf side-letter-b.pdf

/fund smart-contract-sim

Description: Translates a fund's distribution waterfall into programmable logic and simulates execution with sample data. Produces execution traces showing the flow of capital through each waterfall tier, identifies edge cases (e.g., partial catch-up, clawback triggers, recycling loops), and generates pseudocode that can serve as a specification for actual smart contract or financial system implementation.

Usage

bash
/fund smart-contract-sim <file>

Inputs

ParameterTypeRequiredDescription
fileFile pathYesLPA, waterfall description, or existing waterfall model (PDF, DOCX, JSON, or TXT)

Output

Generates SMART-CONTRACT-SIM-[fund-name]-[date].md containing:

  • Waterfall Logic Specification -- formal description of the waterfall in structured format: tiers, conditions, calculations, branching logic
  • Pseudocode Implementation -- language-agnostic pseudocode implementing the complete waterfall, including:
    • Return of capital calculation
    • Preferred return accrual (simple/compound, annual/quarterly)
    • GP catch-up with partial catch-up handling
    • Carried interest split with multiple LP classes
    • Clawback trigger conditions and calculation
    • Fee offset integration
  • Execution Traces -- step-by-step simulation showing capital flow through each tier with sample data sets:
    • Trace 1: Normal Distribution -- standard profitable exit
    • Trace 2: Loss Scenario -- distribution after a loss, partial return of capital
    • Trace 3: Edge Case - Partial Catch-Up -- insufficient distribution to complete GP catch-up
    • Trace 4: Clawback Trigger -- scenario triggering GP clawback obligation
    • Trace 5: Multiple LP Classes -- different preferred return or carry terms by LP class
  • Edge Case Catalog -- identified edge cases in the waterfall logic:
    • Rounding differences across LP allocations
    • Timing of preferred return accrual (daily, quarterly, annual)
    • Recycling provisions and their impact on return of capital
    • Default interest on late contributions
    • In-kind distributions at fair value vs. cost
  • State Diagram -- Mermaid state diagram showing waterfall state transitions
  • Test Vectors -- input/output pairs for validation of any implementation against the specification

Example

bash
/fund smart-contract-sim fund-iv-lpa.pdf

/fund chat

Description: Enters a conversational mode where you can ask natural language questions about fund documents that have been loaded in the current session. Responses include citations to specific document sections, enabling rapid research without manual document searching. Maintains context across the conversation for follow-up questions.

Usage

bash
/fund chat

Inputs

ParameterTypeRequiredDescription
(none)----Activates conversational mode using documents already loaded in the session

Output

Provides interactive responses containing:

  • Direct Answers -- concise answers to natural language questions about fund documents
  • Document Citations -- specific page numbers, section references, and quoted language supporting each answer
  • Cross-Document References -- when the answer spans multiple documents, citations from each source
  • Clarification Requests -- when a question is ambiguous, asks for clarification before answering
  • Follow-Up Suggestions -- related questions the user may want to ask based on the current topic

Example Queries

bash
/fund chat
> What is the management fee during the investment period?
> How does the key person provision work?
> What happens if an LP defaults on a capital call?
> Compare the transfer restrictions in the LPA versus the side letter
> What are the GP's reporting obligations?
> Is there a clawback escrow requirement?

/fund amendment-draft

Description: Drafts a fund document amendment with proper legal format including recitals, operative provisions, track changes notation, and signature blocks. Supports common amendment types and generates language consistent with the original document's style and defined terms.

Usage

bash
/fund amendment-draft <file>

Inputs

ParameterTypeRequiredDescription
fileFile pathYesOriginal document to be amended (PDF, DOCX, or TXT), with amendment instructions included or provided separately

Common Amendment Types

Amendment TypeDescriptionTypical Triggers
Term ExtensionExtends fund term or investment periodApproaching end of initial term, GP request
Fee ModificationChanges management fee rate, basis, or timingMarket conditions, LP negotiation, step-down adjustment
Key PersonModifies key person list, triggers, or remediesPersonnel departure, team changes, succession planning
Investment RestrictionsChanges investment parameters or concentration limitsStrategy evolution, regulatory changes, LP requests
GP Removal / ReplacementModifies GP removal mechanicsGovernance events, restructuring
RecyclingAdds or modifies capital recycling provisionsNeed for additional investment capacity
ERISA / RegulatoryUpdates for regulatory compliance changesNew regulations, guidance updates, examination findings

Output

Generates AMENDMENT-[type]-[fund-name]-[date].md containing:

  • Amendment Header -- amendment number, date, parties, reference to original agreement and any prior amendments
  • Recitals -- whereas clauses establishing:
    • Reference to the original agreement (with date and parties)
    • Authorization for the amendment (required LP consent threshold, LPAC approval, GP authority)
    • Purpose of the amendment
  • Operative Provisions -- for each section being amended:
    • Section reference in the original document
    • Current language (quoted)
    • Amended language with track changes notation (additions in bold, deletions in strikethrough)
    • Effective date of the change
  • Conforming Changes -- other sections requiring update as a consequence of the primary amendment (e.g., updating cross-references, defined terms, schedules)
  • Representations & Warranties -- standard amendment representations (authority, no conflict, binding obligation)
  • General Provisions -- governing law, counterparts, entire agreement, ratification of original agreement except as amended
  • Consent Verification -- required consent threshold per the LPA, method of obtaining consent (written consent, LP meeting, LPAC vote)
  • Signature Blocks -- GP and LP signature pages with entity details

Example

bash
/fund amendment-draft fund-iv-lpa.pdf

This tool does not provide financial, legal, or tax advice.