Legal Ops Depot's AI litigation engine: questions and answers

No. Legal Ops Depot is not a law firm, is not a substitute for an attorney, and does not provide legal advice or legal representation. Disclosures

No. The site describes how the engine works and what the federal rules and statutes say in general terms. It does not apply the law to anyone's facts. If you need advice about a matter, talk to a licensed attorney.

No. Using this site or contacting Legal Ops Depot does not create an attorney-client relationship with anyone.

Legal Ops Depot is the company behind an AI litigation engine and the docket manager, its docket product. "Legal ops" often means in-house legal-operations consulting. See who operates the engine.

It tracks deadlines and prepares court filings. A matter moves through 15 phases, from intake and deadlines through research, strategy, drafting, attack, verification, a final read, a packet check and the filing record. The overview shows the process at a glance.

Litigation work (intake, docketing, research, strategy, drafting and verification) run by software on its own between checkpoints, with a written check on each step and a record of every approval.

Legal Ops Depot is the masterbrand. The main site at legalopsdepot.com is the company; this site, engine.legalopsdepot.com, covers the engine in technical detail.

It is delivered online. It works in a court only once that court's official rule book is loaded; see Which courts are covered?

Law firms and their litigation teams, and people going to court without a lawyer. For law firms · Representing yourself

Civil complaints, led by civil-rights claims under 42 U.S.C. § 1983, and petitions come first. Five matter types have their own pages: civil complaints and civil-rights claims, Supreme Court petitions, post-conviction petitions, appeals and dispositive motions. Each page explains the federal rules and statutes that govern that work and how the engine prepares it.

The headline count is generated from the engine's process file each time the site is built, with the date it was generated: "15 phases · 93 defined steps · 3 checkpoints", as of 30 Sep 2026. Each step has a written check.

How are case citations verified?

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. Each must meet a four-part standard: from the primary source, read in full, supporting the point, and still good law. See how case citations are verified.

What is the Citation Ledger?

The engine's record of verified case citations. Each case citation is one row, with the source it came from, the exact language relied on, its pincite and its verification. When the draft is checked, each case citation in it must match a verified ledger row, or the draft is blocked.

Does the engine rely on what the AI models remember?

Not for authority. The house rule is: "Ideas can come from anywhere. Citations come only from sources." A model may suggest a case as a lead, but a lead is only a candidate until it is fetched from the primary source, read in full and entered in the ledger. Leads from the second model are quarantined until they pass the same check.

What happens to a case mentioned by name only?

A case mentioned by name alone, without a reporter citation, is flagged with a warning rather than blocked.

Are statute and rule citations checked the same way?

No, and the site says so. The Citation Ledger's block covers case citations; statute and rule citations are a declared, separate class. Rule citations are checked against the official rule text the engine fetches for the court. Statute text is required before a statute is relied on, and it is retrieved from the source.

Can the engine invent a case or put a fake citation in a filing?

A model can propose a case that doesn't exist. It can't get a case citation into a filing: the citation needs a verified row in the Citation Ledger, and the engine blocks any case citation without one. That is a rule about process, enforced where the draft is joined to the ledger. It is not a promise that AI never makes mistakes; the process exists because it can.

How does the engine test its own argument?

Plans are written independently and attacked in structured rounds, as opposing counsel would attack them and as a hostile panel would read them. The draft is attacked the same way, and every plausible theory is recorded in a theories ledger as included or excluded, with the reason. Arguments that do not survive are reframed or dropped before you see the draft.

What does the research use?

Primary law: official court rules, the full text of opinions, and the record. Authority is ranked from the highest court that binds the filing court, and binding and persuasive authority are labeled. See what the research uses.

Who checks that a case is still the latest word?

A live search. The sweep for the most recent controlling statement is a written step of its own, run as a live search, and it is recorded as one.

How current is the case law?

The case law and citation graph come from a source snapshot dated 30 June 2026. Before anything is recorded as the most recent controlling statement, a live search is run.

Which AI models does the engine use?

By default, two model families from two different companies, currently Anthropic's Claude and xAI's Grok. Claude is a trademark of Anthropic, PBC. Grok is a trademark of xAI Corp. 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 xAI.

What happens when the two models disagree?

They argue from evidence (the record, the rule text, opinions actually read) for up to three rounds. Agreement is signed with its basis. If they still disagree, both positions and their evidence go up to a checkpoint. A disagreement is never averaged.

What happens if the second model is unavailable?

The matter pauses. It proceeds without the second model only on a recorded, logged waiver. See if the second model is unavailable.

The draft is sent back. On a send-back, the attack and verification checks of phases 11 and 12 are voided and re-run on the new text.

From the face of the document and the rule text, twice by default. A second model recomputes each deadline, and a mismatch is settled by reading the rule. An ambiguous deadline takes the earlier reading. See how deadlines are computed.

Legal Ops Depot's docket product, in your client account. It tracks matters, deadlines, court legs, the clerk's docket entries, activities and a file cabinet. An order that sets no date becomes a watch, and every deadline carries the rule that produced it.

For a law firm, the attorneys of record, who remain responsible for all work product they file. The engine is built to support those duties; it never discharges them. A self-represented filer signs their own papers: under Rule 11(a) of the Federal Rules of Civil Procedure, every paper "must be signed by at least one attorney of record in the attorney's name—or by a party personally if the party is unrepresented." State courts have their own rules.

By default, you approve twice, and the whole filing gets a final read before it ships; each approval, or the client's recorded standing instruction to proceed, is stamped in the record. The checkpoints are the consult, the strategy sign-off and the final read. Safeguards

At the first checkpoint, the problem and the proposed filing type, argued from the record and the official rules. At the second, the strategy, signed off before anything is drafted. At the third, the exact pages to be filed, with a summary of what was corrected and what to watch.

By default, yes: the matter stops at the final read until you approve the exact pages. If a client has recorded a standing instruction to proceed, that checkpoint clears automatically and the clearance is stamped.

A client's recorded instruction for the engine to proceed through the checkpoints on a matter. Each clearance is stamped. It can be revoked at any time, it never lifts a hold, it never skips the candid analysis, and it is not a waiver of the second model.

For a self-represented filer, no: the software prepares the papers, and you review them, sign them and file them with the court yourself. For a law firm, how a filing is submitted depends on the court and on who is filing; ask us about your court.

Which courts are covered?

3,400 courts are matched to their official federal or state court rules, in 57 U.S. jurisdictions, as of 7 October 2026, and research covers state and federal courts up to the U.S. Supreme Court. Local court rules are not loaded yet. The site does not list courts. The engine will not proceed on a court whose rule book is missing.

Can the engine tell whether a case will win?

No. It never promises an outcome. Results depend on the facts, the law and the court.

Do you promise a result?

We commit to a process, not an outcome: every case citation in a filing the engine prepares is a verified ledger row, and the engine blocks any that isn't. No ruling or result is promised. The verification standard

On fictional matters, yes. The board, the gate and every debate shown on this site are hand-built illustrations in the engine's real formats, labeled as such: try the gate. For anything else, email us.

Pricing is on the main site: legalopsdepot.com/pricing (opens the main site). Email us to talk about a matter type and scope. Firms can also request a quote (opens the main site).

Yes. You choose the filing and give it your facts. The software researches the law in our library, applies your court's rules, checks every case it cites and shows your deadline from the rule. You read it, sign it and file it yourself. Legal Ops Depot is software, not a law firm, and does not give legal advice. For legal advice, contact a licensed attorney or a legal aid office.

Matter records and uploaded files are stored in Legal Ops Depot's own Cloudflare account, in a D1 database and R2 storage, which Cloudflare encrypts at rest; see confidentiality and data handling. The privacy page lists what this site collects. For anything else about data handling, email us. See what data the site collects and the terms of use.

The site aims to meet WCAG 2.2 AA. Report a problem on the accessibility page.

On facts for AI assistants and press, with the canonical description and correct names. Terms used on this site are in the glossary: terms defined.

Email contact@legalopsdepot.com.

Start a request (opens the main site)

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