Research from Criterica Intelligence.
Criterica Intelligence publishes numbered working papers, technical notes, standards, data reports and model cards on the outcome, duration and price of legal and regulated assets. Same file, same number, every time.
How to cite Criterica research
Cite a document by its code and version, for example WP-001 version 1.0. Each page ends with a plain citation and a BibTeX entry you can copy, and a PDF that matches the version on the page. A document that changes is issued as a new version with the change recorded, so a citation always points to the text you read. DOIs are pending and each document says so.
Numbered documents
- WP-001Time-at-Risk: A Metric Family for Legal-Asset DurationWorking Paper · Version 1.0 · 3 August 2026
Credit has ratings and market risk has value at risk, while legal assets have had adjectives. This paper defines six measures of duration risk: TaR90, Excess TaR, Duration Drift, Cash-at-Date, Delay Concentration and Recoverable Time. Each carries a formula, a unit and the decision it feeds. Five are computed from the public federal record; Recoverable Time is defined but not computed, because public data holds no intervention histories.
- WP-002The Seven Clocks: Why Litigation Duration Is Not One NumberWorking Paper · Version 1.0 · 3 August 2026
A duration estimate such as "about 36 months" is seven forecasts under one name: seven processes with different drivers, endpoints, data and responses to intervention. This paper separates them. It then re-estimates one matter from the public federal record four times to show why duration must be a living distribution with preserved history, and not a number spoken once at underwriting.
- WP-003Duration and Returns: The Arithmetic of Time in Litigation FinanceWorking Paper · Version 1.0 · 3 August 2026
A multiple is time-blind and an annualized return is not. This paper works through what that asymmetry does to legal-asset economics using arithmetic any reader can verify by hand: the sensitivity of IRR to duration at a fixed multiple, the convexity of the clock, four effects kept separate, portfolio tails and capital velocity. No model output appears in it.
- TN-001Methodology: How the Numbers Are DerivedTechnical Note · Version 1.0 · 9 October 2026
This note states what a production model means at Criterica, how a model earns that label, how the court-record corpus is built, how often models are retrained and which published figures come from third parties. It separates measured quantities from third-party estimates and from illustrative figures, and it states which basis is available to institutional counterparties on request.
- TN-002How We Build ModelsTechnical Note · Version 1.0 · 9 October 2026
This note describes the lifecycle of a Criterica production model in seven stages, from real filed records and jurisdiction-specific training through temporal holdout evaluation and promotion gates to a versioned registry and scheduled retraining. No stage is optional and none is waived. It is the same pipeline description given in diligence.
- STD-002The Criterica Score SpecificationStandard · Version 1.0-rc · 9 October 2026 · Request for comment
This specification defines the Criterica Score: a number from 0 to 100 attached to one legal asset, portfolio or counterparty at a stated date, against a stated reference population and horizon. It sets the mapping, the Not rated rule, the sealed-outcome rule, validation status by asset class, versioning and governance. It is issued as a request for comment.
- MC-001The Model Registry and Public ChangelogModel Card · Version 1.0 · 9 October 2026
This record states how Criterica decides what counts as a production model: the promotion gates, the full record of models that did not make it, and the public methodology changelog. Each model is cleared individually, every attempt stays on the record and corrections are recorded alongside improvements.
Related standard: The Legal Asset Integrity Standard (Criterica Group). Subscribe by RSS.
Jurisdiction-specific models, not generalist classifiers.
General-purpose legal AI trains on pooled case data across hundreds of jurisdictions and expects a single model to generalize across venue, bench composition, and procedural history. The prediction error from that pooling is not recoverable. Jurisdictions differ structurally, not just in volume. A model trained on California commercial litigation will systematically mispredict outcomes in the Fifth Circuit or Northern Ireland. Criterica trains one model per jurisdiction per case type, narrow and deep, tuned on the actual caselaw of that venue. The fleet spans production models across federal circuits, state appellate courts, and specialist tribunals. No model is asked to generalize beyond the cases it was trained on, and that constraint is architecturally enforced, not advisory.
Real court records. No synthetic augmentation.
Synthetic training data in legal AI is a compounding error: a model trained on AI-generated case summaries learns the statistical patterns of another model, not the patterns of actual judicial behavior. Every Criterica model trains exclusively on real filed records from federal and state dockets, international tribunals, and regulatory enforcement actions. The training corpus is deduplicated, outcome-labeled, and temporally partitioned before any model sees it. Training sets are partitioned by filing date so a model is never trained on cases it should not yet be able to see. Our proprietary outcomes corpus provides the primary US backbone, supplemented by state court filings, licensed industry datasets, and international tribunal data from England, Wales, Australia, and Canada. Zero synthetic rows appear anywhere in the production fleet.
A reliable probability, not a sentiment label.
Most legal AI returns text: a summary, a risk flag, a qualitative category. Criterica outputs a structured score set for each matter: a risk score (0–100), risk band (Low / Moderate / Elevated / High / Critical), recovery probability (0.0–1.0), damages range (low / expected / high), a recommendation (FUND / CONDITIONAL / PASS), model confidence, and the list of models applied. Reliability is measured on cases the model never saw, partitioned at the circuit level. A 0.73 output means a 73 percent prediction is right about 73 percent of the time in real outcomes, not that it "feels likely." Outputs are audience-configurable: Capital Provider, Law Firm, and Insurer views are derived from the same model layer, structured per decision context. The output feeds a spreadsheet, a risk model, or a funding committee. It is not a narrative. That distinction is intentional.
Performance thresholds enforced at promotion. No exceptions.
Models that do not clear the promotion threshold, tested against real outcomes for how reliably they predict, remain in stub status regardless of sample size or elapsed time. Circuit-level models currently in production are tested on cases they never saw and held to a consistent reliability bar across case type and jurisdiction. Models that score perfectly are flagged as suspect and held for review before promotion, because a result that looks too good almost always means the model had effectively seen the answer in advance, not that it found a real signal. Known problem patterns, including formula-based statutory outcomes and circular features, are identified during training review and either excluded or permanently flagged as non-promotable. A small number of models remain in experimental or suspended status pending additional data or review. The registry records every model's training date, training row count, feature vector, performance, and promotion decision, and that record is permanent.
Statistics shown reflect historical or illustrative model outputs derived from real case data. They are not predictions or guarantees of any individual outcome. Litigation results depend on facts, jurisdiction, judge, and counsel, and vary case by case. Model accuracy is subject to selection effects and changing legal dynamics.
The corpus and the promotion gate are documented in the methodology note.
Test the method on your own file.
An audit runs the published method on your tape or schedule and returns a written read. The monthly brief carries each new release by email.
Questions
Every document in the series carries a code, a version and a date, with a plain citation and a BibTeX entry at the foot of the page. Cite the code and version, for example WP-001 version 1.0, so a reader can find the exact text you relied on.
Not yet. Each document shows DOI: pending until one is registered. The code, version and URL identify the document in the meantime, and a version that changes is issued as a new version, not edited in place.
Yes. The research feed is an RSS file at /research/feed.xml and lists every document with its abstract. The monthly brief carries the same releases by email.
No. The working papers use arithmetic and the public federal record, and the documents that describe models state their method and their limits. Nothing in the series predicts any individual matter.