Litigation Finance, with structure-aware discipline

Cases are idiosyncratic. Each matter has its own duration, jurisdiction, court schedule, probability distribution and payoff structure. Portfolio analytics need to aggregate this heterogeneity.

Duration is court-driven. Case duration depends on court schedules, appeals and settlement dynamics rather than a fixed maturity. Portfolio duration needs to model these dynamics.

Outcomes are contingent. Payoffs depend on case outcome, settlement, appeal and enforcement. Multi-outcome scenario modelling is the underwriting standard.

Confidentiality is structural. Case detail carries confidentiality obligations. Access controls and information barriers need to be first-class, not bolted on.

Litigation Finance carries 4 sub-asset overlays in the Reuben AI rubric registry: Single case, Portfolio funding, Law firm lending and Judgment enforcement and awards. Those overlays are part of the 314 sub-asset overlays the platform maintains across 56 of its 68 native asset classes.

An overlay never reweights the parent rubric. It adds the extra scoring criteria, risk flags, document types and key term fields that only apply to that slice, so a single case deal and a judgment enforcement and awards deal are both scored on the shared litigation Finance rubric while each is still asked the questions specific to its structure. That is what keeps deals inside one asset class comparable to each other and to the rest of the portfolio.

Selecting an overlay at intake changes what the platform expects: the document checklist, the extraction schema for key terms, and the flags raised when a term sits outside the range the rest of your litigation Finance book has accepted. Nothing is retrofitted later by hand.

Every litigation Finance opportunity that moves through Reuben AI leaves a structured record rather than a folder of documents and a memo. The rubric score is stored with the criteria that produced it, each extracted key term is stored with the clause and page it came from, and every flag is stored with the reason it fired and who cleared it.

The practical effect is that the investment committee paper, the LP report line and the audit trail are all reading the same underlying record. When an LP asks in year three why a litigation Finance position was underwritten the way it was, the answer is retrieved, not reconstructed.

Litigation Finance is a specialist allocation rather than a core one, relevant to a narrow set of mandates and held opportunistically elsewhere.

That matters operationally because most funds do not hold litigation Finance alone. The moment a portfolio spans more than one asset class, comparability becomes the constraint: a position scored on a bespoke litigation Finance spreadsheet cannot be ranked against a position scored somewhere else. Running litigation Finance on the same rubric engine as the rest of the book removes that break.

Reporting inherits the same property. Portfolio monitoring, valuation cadence, capital account movement and LP reporting all draw from the single stored record, so a litigation Finance position appears in the quarterly pack on the same basis as every other holding, with the same evidence behind it.