New on SSRN: Ariadne's Thread, a measurement-theoretic method for legal openness. Read the paper
Verification and Usable Law

What does it take for a legal proposition to be safe to rely on?

Moving verification from 'is this case good law' to 'is this proposition usable here, now, for this client'.

11 pieces · 6 theses · 4 frameworks · Program RSS

Plate 21 · Proposition in CrystalPlates
Why it matters

Verification, as the profession now practices it, asks whether a case is good law. Attorneys need the answer to a narrower and harder question: whether this proposition, drawn from this case, is usable here. A holding can be real, accurately quoted and clean in every citator, and still be dead as a proposition, displaced in this forum, announced under a different procedural standard, adverse to the client, or already offered to a court in this jurisdiction and rejected. None of those failures announces itself. Opposing counsel may miss them. The court may miss them. The client never sees them.

This program builds the vocabulary and the protocols for closing that gap. The Proposition-Usability Model, set out in Good Law for What?, replaces one question with four: is the proposition still valid, does it govern in this forum and posture, whom does it help, and has the argument already been rejected. The Case Treatment Taxonomy classifies treatment at the level of the holding, by scope, severity and mechanism, because one opinion can overrule one holding, distinguish another and follow a third. The Posture Mismatch Taxonomy names the failure no citator flags: right law, wrong stage. The Completeness Protocol turns to what a brief leaves out, because motions are lost on the complement as well as on the contents.

Why this matters: citation checking has become the profession's default answer to AI risk, and it is a legitimate control. But it inspects citation-sentence pairs. It cannot see the wrong standard applied correctly, the controlling adverse case that was never pulled, or the argument this court has already refused. A verification layer is a smoke alarm, not a building code. The work here is to specify what the building code should say, in terms a librarian, a judge or a malpractice carrier can apply without trusting any vendor, the Institute's own sponsor included.

Everything in this program

All pieces, newest first

20 Sep 2026The Smoke Alarm ProblemWhat Happens on Monday Morning When a Firm Relies on a Citation VerifierMarcus Hale · 9 min readEssayVerification20 Sep 2026The Verification Layer Is a Smoke Alarm, Not a Building CodeWhy "just verify it" is the laziest idea in legal AIRoss Brodskiy · 7 min readEssayVerification1 Sep 2026Good Law for What?A Proposition-Usability Model for Verification in AI-Assisted Legal ResearchRoss Brodskiy and Nathan Pokov · 6 min readPaperVerification1 Sep 2026What a Filing-Grade Benchmark Must MeasureDispositive recall under doctrinal and procedural constraint, and why fabrication rate is no longer the headlinePriya Raman · 12 min readField GuideSystem Design18 Jul 2026Posture, Standard, and the Shape of DiscretionA review of Brodskiy and Pokov, Ariadne's ThreadEleanor Voss · 6 min readReviewDeterminacy26 Jun 2026Research the Carrier Won't Pay ForWhat a Small Defense Firm Should Demand from Legal AINora Kestrel · 6 min readEssayAdversarial26 Jun 2026Right Law, Wrong StageProcedural Posture as the Failure No Citator FlagsEleanor Voss · 8 min readEssayVerification26 Jun 2026The Case You Never PulledA Pre-Filing Completeness Protocol for Dispositive MotionsAda Mercer · 8 min readEssayVerification26 Jun 2026The Docket TestHow to Evaluate Legal AI for Dispositive Motions in One AfternoonTom Brennan · 5 min readField GuideSystem Design26 Jun 2026Twombly Doesn't Live HereWhy AI Trained on Federal Practice Gets State Pleading WrongMarcus Hale · 7 min readEssayVerification2 Apr 2026Case Treatment Classification GuideCan I still rely on this case, and if so, to what extent?Ross Brodskiy · 2 min readField GuideVerification