Legal Ops Depot AI litigation engine, home Start a request (opens the main site)

AI LITIGATION SOFTWARE · LAW LIBRARY

Autonomous litigation, built on primary law.

Start a request (opens the main site) Search the law library free (opens the main site)

Not legal advice. Not an attorney.

Part A: the engine builds your filing to your court's official rules. Part B: our law library, free to search, for you and your AI. Get the free connector (opens the main site)

Litigation software built to prevent hallucination, for the filings where one error ends the case: civil complaints, including civil-rights claims under 42 U.S.C. § 1983, and petitions, from post-conviction to the U.S. Supreme Court. Every matter runs through the same structured 15-phase process, researched in our own law library, never from a model's memory. The highest authority that binds your court comes first, and every opinion is read in full before it is cited. By default, two AI models from two different companies, Claude and Grok, then attack the work the way the other side will.

Pro se? How the engine works for you.

  • Hard data, not trained data. The law comes from our own library, and every case citation is checked against the full opinion before it can appear.
  • Highest authority first. Research climbs to the court that controls yours, searches as hard for the law against you as for you, and says so plainly when no court has decided the point.
  • Your court's own rules. The official rule text for the court and the filing type is pulled and checked before drafting.
  • It attacks its own work. A second model and a hostile-judge read try to break the argument before the other side can.

PART A · THE ENGINE

Litigation that checks itself.

What you're watching is the engine's own status board. Every matter moves through the same 15 phases and 94 defined steps, an AI process built to prevent hallucination: it works only from hard data in our own law library, never from a model's trained memory, and it starts from the highest-authority case law that binds your court.

Engine board: five fictional demo matters moving through 15 phasesIllustration with fictional matters, not a live run. Each light has a shape and a label: pending, active, done, paused at a checkpoint, blocked, bypassed (express) and kicked back. Brass gates after phases 5, 8 and 14 are the three checkpoints. Demo A is drafting in phase 10. Demo B is paused at phase 5 for the consult. Demo C was kicked back from the final read in phase 13 to drafting in phase 10, so the attack and verification checks of phases 11 and 12 are void and re-run. Demo D is blocked at phase 3. Demo E bypassed phase 4 on the express path and is researching in phase 6.ENGINE BOARDILLUSTRATION · FICTIONAL MATTERSCaptureUnderstandResearchArgueBuild and attackProveFileActPhase010203040506070809101112131415123DEMO AAppealDEMO BCivil-rights complaintDEMO CPost-conviction motionDEMO DResponse to a motionDEMO EPetition for reviewPendingActiveDonePaused at a checkpointBlockedBypassed (express)Kicked backCheckpointKickback voids and re-runs the attack and verification checks of phases 11 and 12. Each brass gate is a checkpoint. Engine board, phone layout: four fictional demo matters across 15 phasesIllustration with fictional matters, not a live run. Demo B is paused at phase 5 for checkpoint 1. Demo C was kicked back from phase 13 to phase 10, so the attack and verification checks of phases 11 and 12 re-run. Demo D is blocked at phase 3. Demo E bypassed phase 4 on the express path and is active in phase 6. Brass bars after phases 5, 8 and 14 are the checkpoints.ENGINE BOARDFICTIONAL156891415DEMO BCivil-rights complaintPaused at checkpoint 1DEMO CPost-conviction motionKickback 13 → 10: phases 11–12 re-runDEMO DResponse to a motionBlocked at phase 3DEMO EPetition for reviewPhase 4 bypassed (express)PendingActiveDonePaused at a checkpointBlockedBypassed (express)Kicked backCheckpoint
Illustration: fictional matters, hand-built in the engine's real formats. No real matter is shown.

The matters on the board are invented. Each row is a matter; each column is a phase. Watch one pause at a checkpoint for review, and a draft get sent back for rework, which re-opens its attack and verification checks.

Legal Ops Depot's AI litigation software helps law firms and self-represented filers draft civil complaints, § 1983 civil-rights claims and petitions: by default, two models from different companies research primary law in its library, attack the argument and verify every case citation against the full opinion. Legal Ops Depot is not a law firm and does not give legal advice.

THE FILING TRACKER

Watch your filing move, stage by stage.

Every matter has its own page in your client account. It shows the same 15 phases the engine works through, lit as each one finishes, so you can see where your filing stands without asking anyone.

Progress Working

Avery v. City of Example (fictional) · Response to motion to dismiss

Stage 10 of 15: Drafting · 9 done

Illustration: the filing tracker as a client sees it, drawn from the live page with a fictional matter. No real matter is shown.
  • Every stage, lit as it finishes. Done, in progress or not started, at a glance on your phone or desk.
  • Each stage, step by step. Open any stage to read a short summary of it and the steps listed for it, each marked by where it stands.
  • Your filing packet, beside the court's checklist. Read a PDF or text paper on the page or download any paper, next to the court's filing checklist from the official rules on file. Local rules are not loaded. A scanned exhibit may show blank in the reader for now; download it to see it.
  • Deadlines in your own calendar. Make one private link for iPhone, Google Calendar or Outlook, with reminders a week and a day before. Always check the dates against the court's order and rules.
  • Check a draft's citations. Paste a draft, and each reporter citation, up to 60 per check, is looked up in the law library: whether the case is there, whether the name matches, and any red or yellow flag. It is a library lookup, not legal advice.
  • The court's docket is the record. What the court has done is recorded from the court's docket.
  • Bring your own AI to the matter. Add the connector, and your AI can read the matter and the files shared with your account. It can read only; it cannot change, file or delete anything.
  • Your matters, and only yours. A client account sees its own matters, never another client's.

Create a free account (opens the main site) See the filing tracker (opens the main site) How deadlines are tracked

Built for the filings where one error ends the case.

The engine is built around civil complaints, above all civil-rights claims under 42 U.S.C. § 1983, where a thinly pleaded element or an unanswered immunity defense can end a case before anyone reaches the merits. Petitions sit beside them: post-conviction petitions, where timing rules can bar a claim, and petitions to the U.S. Supreme Court, where what was preserved below decides what can be asked. Appeals and dispositive motions run through the same process. For each claim, a preservation map shows where it must be raised now to stay alive in every court above, and whether the matter raises an issue of first impression. When controlling law cuts against the theory, the work stops until there is a recorded change of course.

How the engine handles the hardest cases

  • Civil complaints and civil rights. Civil complaints, including § 1983 claims, with each element mapped to a paragraph, a record citation and a verified authority, and immunity defenses anticipated.
  • Supreme Court petitions. Built to the Court's own rules, preservation first.
  • Post-conviction petitions. State post-conviction and federal habeas, each named correctly, with the limitations clocks docketed.
  • Appeals. Preservation, the standard of review for every issue, and record citations checked against the record.
  • Motions. Dismissal and summary-judgment practice built on an element-by-element sweep.

PART B · THE LAW LIBRARY

A real law library. For you, your AI, and the engine.

The same library the engine researches in is open to you. Search court opinions, statutes, regulations and court rules free on legalopsdepot.com, add it to Claude, Grok or any AI app that supports custom MCP connectors, or call it from your own software. The free plan needs no card and includes a daily allowance of lookups; paid plans raise it. See current plans on the pricing page (opens the main site).

Search the law library (opens the main site) Connect your AI assistant

  • about 10 millioncourt decisions
  • 77.5 millioncitation links ranking authority
  • 3,400courts matched to their official court rules, in 57 U.S. jurisdictions
  • 50 states + federalstatutes, plus the Code of Federal Regulations

Case law from a source snapshot dated 30 June 2026; court rules as of 7 October 2026.

The engine doesn't research from a model's memory. Its AI models start from scratch in Legal Ops Depot's own law library of case law, statutes and court rules. They read every opinion in full before relying on it, to confirm it supports your point and to surface what cuts against it. A model's training is only a backup: it can suggest where to look, never what to cite.

Every case relied on is read in full from a primary source before it is cited.

Research ranks authority from the highest court that binds the filing court. Binding and persuasive authority are labeled, state and federal law are both covered up to the U.S. Supreme Court, and a search in both directions looks for controlling authority against the theory. If it finds some, the work stops until there is a recorded pivot.

Official rule text is fetched before strategy and re-checked before drafting and before the final read. Statute text is required before reliance, and it is retrieved from the source. A live search checks recency. Read more about research from primary law.

Your AI gets the library too.

Connect your firm's AI agent, or your own, to the same library through our MCP connector. Your agent can look up a case by citation and read the full opinion, pull a statute section, search a court's rule text and rank the strongest authority on a point. The connector is read-only: it looks things up and cannot file, edit or delete anything.

No lawyer? Connect your own AI to the same law library and research your case yourself.

  1. Copy the connector URL from the connector page.
  2. In Claude, open Customize > Connectors, click "+ Add", then "Add custom connector", and paste the URL. Grok and any other app that supports custom MCP connectors can use the same URL.
  3. Sign in with your Legal Ops Depot account.

Free to start, with paid plans on legalopsdepot.com for more daily use.

Get the free connector (opens the main site)Not legal advice. How to connect

The connector returns the law, not advice about your case.

Verified. Adversarial. Autonomous. Operational.

Four words describe how the engine works, in this order. Verified: the research and every case citation come from primary sources, with receipts. Adversarial: a hostile-panel read and, by default, a second model family try to break the argument before anyone else can. Autonomous: the work moves between the 3 checkpoints on its own and stops at the checkpoints where, by default, the work is reviewed. Operational: deadlines, docket entries and many matters at once, each through the same checks, with throughput governed by quality. Firms run many matters at once; a self-represented filer runs one, through the same checks.

THE UNVERIFIED-CITATION RULE

Ideas can come from anywhere. Citations come only from sources.

Every case citation is pulled from the primary source, read in full, and verified before it can appear in a filing. A case citation that is not in the verified ledger cannot reach the page.

A model may suggest a case. It may not cite one. Each case citation must meet a four-part standard before it becomes a row in the matter's citation ledger:

  1. Primary source. The opinion is fetched from a primary source, never recalled from a model's memory.
  2. Read in full. The whole opinion is read, and any quotation is taken word for word from it, with a pincite.
  3. Supports the point. The holding and the disposition fit this issue in this posture, not just a phrase in the opinion.
  4. No later decision found overrules it. The research looks for later decisions that cite it. Only overruled U.S. Supreme Court decisions are flagged automatically, so read the limits.

Before a document can go out, each case citation in the draft is matched against the ledger. No row, no citation.

No unverified case citation can reach a filing: the engine blocks it.

The block covers case citations. Statute and rule citations are declared as their own class and checked by other steps. How the block works

1Primary source
2Read in full
3Supports the point
4No later decision found overrules it

15 phases · 94 defined steps · 3 checkpoints

Each with a written check. Count generated from the engine's process file, as of 23 Oct 2026.

Intake → Docket and deadlines → Case file → Record review → Vehicle and elements → Checkpoint 1: the consult → Research → Second-model consult → Strategy → Checkpoint 2: strategy sign-off → Filing blueprint → Drafting → Attack → Verification → Final read → Packet check → Checkpoint 3: final read → Filing record and follow-through

See all 15 phases

Two models. One standard.

By default, two model families review the work; if the second is unavailable, the matter pauses, and it proceeds without it only on a recorded, logged waiver. The two are currently Anthropic's Claude and Grok. The second model family reads the complete record on its own, proposes its own strategy, hunts for authority the first pass missed and recomputes deadlines. Its citations are leads only: each must pass the same verification before it can be used. The two do not vote and they do not average. Each side argues from evidence only: the record, the rule text, opinions actually read. Agreement is recorded with both signatures and its basis. If they still disagree after three rounds, both positions and their evidence go to the next checkpoint.

Watch the models argue

Illustration, fictional matter. Hand-built to show the engine's real formats. The matter, parties, courts and dates are invented.

Deadline cross-check · Avery v. City of Example (fictional) · round 1 of 3

Claude · position. The City filed its motion to dismiss on Tuesday, December 1, 2026. The scheduling order (fictional), ¶ 3, gives 21 days after the motion is filed to respond, so the response is due Tuesday, December 22. Basis: docket entry; scheduling order ¶ 3 (fictional); Fed. R. Civ. P. 6(a)(1).

Grok · counter, with evidence. Same filing date, one more source. The assigned judge's standing order (fictional), ¶ 4, sets 14 days to respond to a motion to dismiss. On that reading the response is due Tuesday, December 15. Basis: standing order ¶ 4 (fictional); scheduling order ¶ 3 (fictional); Fed. R. Civ. P. 6(a)(1).

Claude · reply. Agreed: two written rules in the record give two periods, so there are two readings. The engine's rule for an ambiguous deadline is to docket the earlier one.

Claude / Grok · AGREED: docket the response for Tuesday, December 15, 2026, the earlier reading; note the scheduling-order reading in the entry. Basis: standing order ¶ 4 (fictional); scheduling order ¶ 3 (fictional); Fed. R. Civ. P. 6(a)(1).

Claude is a trademark of Anthropic, PBC. Grok and other names are trademarks of their respective owners and are used only to describe the technology in our process. Legal Ops Depot is not affiliated with, sponsored by or endorsed by Anthropic or the maker of Grok.

Two model families from two companies

It attacks its own work before anyone else can.

Before you see a strategy, the plans are attacked as opposing counsel would attack them and read as a hostile panel would read them. After drafting, the draft is attacked again, and every point a skeptical court could skip is rewritten so that skipping it becomes visible, reviewable error: the record cited, the objection stated, the standard of review named. On the full lane, the second model family can also be asked for the three strongest attacks the other side will make, each with the counter that answers it. If the final read sends the draft back, the attack and verification checks of phases 11 and 12 are voided and re-run on the new text. See how the engine attacks its own argument.

Illustration · fictional

Point How an unreceptive panel could avoid it Rewritten so avoiding it is visible error
Exclusion of the (fictional) witness's testimony Treat the issue as never preserved "Plaintiff made an offer of proof (R. 212–14), and the court ruled on it (R. 215). The issue is preserved under Fed. R. Evid. 103(a)(2). Standard of review: abuse of discretion."
The limitations question Rely on the order's paraphrase of the rule Quote the governing text in full, including the clause the paraphrase leaves out, and cite where it was argued below (R. 88).
The City's immunity defense Decide it on a ground the City never raised "The City argued only one ground below (R. 40–46). No other ground was pressed or passed upon."

Deadlines, computed twice by default

Every incoming document becomes a docket entry or a written note saying why it sets no deadline. Deadlines are computed from the document's face and the rule text, and an ambiguous deadline takes the earlier reading. By default a second model recomputes each one. A mismatch is settled on the rule text, never averaged, and one that can't be settled comes to you. An order that sets no date gets a watch entry, never an invented date. The docket product is the filing tracker, in your client account.

Your docket lives in the software: every deadline, the rule it comes from, and where each filing stands.

Deadlines, computed twice by default

Illustration · fictional

RESPONSE TO MOTION TO DISMISS · Avery v. City of Example (fictional)
Computation A (Claude) ... Tue 22 Dec 2026 · scheduling order ¶ 3 (fictional); Fed. R. Civ. P. 6(a)(1)
Computation B (Grok) ..... Tue 15 Dec 2026 · Standing order ¶ 4 (fictional); Fed. R. Civ. P. 6(a)(1)
Status .................. MISMATCH · AGREED in round 1 · docketed to the earlier reading
Watch ................... the City's reply period opens when this response is filed

Built for self-represented filers, too.

The court holds you to the same rules as a lawyer. The software checks your papers against them.

  1. You choose the filing. Pick what you're filing and tell your side in your own words.
  2. Real law, read in full. The software researches it in our law library, highest authority first, and reads every opinion before it cites it.
  3. Your court's own rules. The papers are built to your court's published format, page limits and required companion documents.
  4. Your deadline, from the rule. Enter the date on the paper you received, and it shows the date your court's rule gives, with the rule text beside it so you can check it.

You read it, sign it and file it yourself. Legal Ops Depot is software, not a law firm. It doesn't give legal advice, and you decide what to file. Representing yourself: the full guide.

Open the work catalog (opens the main site) How it works

Autonomous between 3 checkpoints.

The engine works on its own between 3 stops. By default, the work stops twice for review, and the whole filing gets a final read before it ships; each review, or the client's recorded standing instruction to proceed, is stamped in the record.

  1. The consult. After intake, you decide what the problem is, what the client wants, and which filing fits.
  2. Strategy sign-off. Before drafting: the plan after it has been attacked, and for law firms, the one-page assessment.
  3. Final read. Before filing: the exact pages to be filed.

This is the default full lane. A routine filing can run in an express lane without the strategy stage. A client can record a standing instruction to proceed; it is stamped at every checkpoint it clears, it never lifts a hold, and the candid analysis still runs. The 3 checkpoints

Set it, supervise it, sign it.

Hand the engine the file; get back a court-ready draft, a live docket and a receipt for every case citation. The firm's attorneys supervise the work and remain responsible for what is filed; the engine is built to support those duties and never discharges them.

How firms supervise and sign

Not a chatbot. A fail-closed, multi-model pipeline with receipts.

The process is data, not a prompt. Every step has a written check, and gates are tested to prove they can fail. Wherever the roles allow, the builder, the verifier and the final reader are separate. A case citation is joined to its ledger row by reporter, volume and first page, never by name.

The architecture, for engineers

Questions people ask first

Is Legal Ops Depot a law firm? No. Legal Ops Depot is not a law firm and does not give legal advice, and using the site or the service creates no attorney-client relationship. Read what Legal Ops Depot is not.

Can the engine make up a case? A model can suggest one; it cannot cite one. A case citation reaches a filing only as a verified row in the matter's citation ledger, and the engine blocks any case citation without one.

Is the work reviewed? By default, the work stops twice for review, and the whole filing gets a final read before it ships: the consult, the strategy sign-off and the final read. A client may instead record a standing instruction to proceed. Each review, or that standing instruction, is stamped in the record. The safeguards page sets out its limits.

Which AI models does it use? By default, two model families from two different companies, currently Anthropic's Claude and Grok. Neither can overrule the other, and a disagreement is never averaged. If the second family is unavailable, the matter pauses, and it goes on without it only on a recorded, logged waiver.

Which courts does it work in? 3,400 courts are matched to their official court rules, in 57 U.S. jurisdictions, as of 7 October 2026, and the engine will not proceed on a court whose rule book is missing.

Who is behind the engine? Legal Ops Depot, the company behind legalopsdepot.com. Read about Legal Ops Depot.

More questions

What the engine is

The engine: the facts

Checked 27 October 2026. Every number carries its own date.

Fact Detail
Category AI litigation software and a law library.
Tagline "Ideas can come from anywhere. Citations come only from sources."
Made by Legal Ops Depot, for courts across the United States. The company's main site is legalopsdepot.com.
Web address engine.legalopsdepot.com
Client accounts Each client has their own account, with a filing tracker that shows where every piece of work stands and the rule behind each deadline. The filing tracker in your client account tracks matters, deadlines, court legs, the clerk's docket entries, activities and a file cabinet.
The process 15 phases · 94 defined steps · 3 checkpoints, each step with a written check (generated from the process file, as of 23 Oct 2026).
The citation rule Every case citation is pulled from the primary source, read in full, and verified before it can appear in a filing. A case citation that is not in the verified ledger cannot reach the page.
The models By default, two model families from two different companies, currently Anthropic's Claude and Grok. If the second is unavailable, the matter pauses; it proceeds without it only on a recorded, logged waiver.
Your control By default, the work stops twice for review, and the whole filing gets a final read before it ships; each review, or the client's recorded standing instruction to proceed, is stamped in the record. A standing instruction never lifts a hold, and the candid analysis still runs.
Research library Legal Ops Depot's own law library: about 10 million court decisions and 77.5 million citation links, from the 30 June 2026 source snapshot. Every case relied on is read in full from a primary source before it is cited.
Court rules 3,400 courts matched to their official court rules, in 57 U.S. jurisdictions, as of 7 October 2026.
Connector Create a free account and connect your AI agent to Legal Ops Depot's legal research connector: court opinions, citations, statutes and court rules, through the Model Context Protocol (MCP). Read-only. Every account, Free included, also gets API keys. Not legal advice. How to connect · Plans (opens the main site) · API details (opens the main site).
Catalog Order a filing from the catalog, priced per filing.
Statutes Statute text is required before a statute is relied on. Statute text is retrieved from the source.
Where it works It is delivered online, for courts across the United States. It works in a court only once that court's official rule book is loaded. There is no office to visit; the mailing address is for mail only.
Who it serves Law firms and their litigation teams, and self-represented filers (people going to court without a lawyer).
What it is not Not a law firm. Not legal advice. Using it creates no attorney-client relationship. It never promises an outcome.
Contact contact@legalopsdepot.com

Claude is a trademark of Anthropic, PBC. Grok and other names are trademarks of their respective owners and are used only to describe the technology in our process. Legal Ops Depot is not affiliated with, sponsored by or endorsed by Anthropic or the maker of Grok.

Ask about the engine

Questions about how the engine handles a matter, phase by phase and checkpoint by checkpoint? Write to us through the contact page.

Start a request (opens the main site)

Legal Ops Depot is not a law firm and does not give legal advice.

Legal Ops Depot logo