Use AI for legal review you can prove
Your teams use AI for privilege calls, briefs, and invoices. When a court, a client, or opposing counsel asks how the work was done, you need to show your rules were applied every time. Jaxon is the verification layer that checks each AI output against your protocols, court rules, and outside counsel guidelines, then returns TRUE, FALSE, or UNKNOWN with a defensible audit trail.
The rules the court, opposing counsel, and your clients will ask about. Jaxon encodes them.
Four facts that frame every conversation about AI in legal practice.
AI hallucination cases identified in U.S. court filings, with courts issuing sanctions and disciplinary referrals.
Source: AI Hallucination Cases database (Damien Charlotin), November 2026
Every rule resolves to TRUE, FALSE, or UNKNOWN, with an audit-ready trail behind the verdict.
Mid-sized law firms that have formally adopted generative AI, while 81% of firm leaders report concern about its reliability.
Source: SurePoint 2025 State of the Legal Industry, via LawSites
Protocols encoded once, applied to every document and reused across matters.
AI is already making first-pass relevance and privilege calls. Opposing counsel wants to know how you checked them.
A privilege claim with no attorney on the thread, or a brief citing a case that does not exist, is a challenge in the making. Without a deterministic check, prompt engineering and RAG reduce error rates but cannot show a court how each call was made.
Jaxon is an API that runs inside your review platform, document management, and e-billing systems. There's nothing new to log into.
The integration. A single API connection that your existing systems call.
The rules. Discovery counsel, litigation support, and knowledge management approve every protocol before it runs.
Replaces ad-hoc prompt engineering with a version-controlled compliance layer.
How DSAIL® verifies AI outputs instead of letting one model grade another.
Most AI checks ask a second model to grade the first. That's still a probability, and you can't defend a probability at a meet-and-confer. Jaxon splits the work. The AI reads the document and answers narrow factual questions, like whether an attorney is on the communication. Your rules, written in DSAIL (Domain-Specific AI Language), then decide the verdict the same way every time. The rules never live inside a prompt.
The probability path
One model grades another
92% confident means wrong 8 times in 100, and no way to tell which.
Illustrative
The proof path
The AI reads. Your rules decide.
A model that cannot say it does not know will guess. UNKNOWN is where the guess would have been.
A proof. Produced at the meet-and-confer, in the motion, to the client.
Defensible like human review, and fast like the AI it checks. Audit-grade output at API speed.
What Jaxon delivers to your litigation and practice teams
Discovery Counsel · Litigation Partners · Litigation Support · Knowledge Management · Firm General Counsel
Consistent calls
Every document is checked against the same encoded protocol, with no variance between reviewers.
An audit-ready trail
Every recommendation traces from protocol text to rule, extracted fact, and source passage.
Exception-only workload
Jaxon clears the routine entries; attorney judgment goes to the FALSE and UNKNOWN results.
A record you can produce
When a call is challenged, you can show the client, the court, or opposing counsel exactly how it was made.
What Jaxon delivers to your engineering team
CIO · Litigation Support Director · eDiscovery Engineering · Information Security
Weeks, not quarters
Jaxon is an API, not a platform migration. A pilot runs on exports with no integration.
Model-agnostic
Works with GPT, Claude, Gemini, or whatever model your firm has approved, including models running in your own Azure, AWS, or Google Cloud account. Rules are written once and updated when a protocol changes, with no retraining.
Deploy where data must stay
Deployable in your own cloud tenant or on-premises. Jaxon does not host, store, or process client data.
Clean separation
Change a rule without touching the AI, or switch AI models without rewriting your rules.
The only approach that got every rule right, every time
In DSAIL® Benchmark 3.0, DSAIL went up against the three ways teams usually try to make language models reliable: careful prompting, retrieval-augmented generation (RAG), and a second model acting as judge. Same models, same documents, 65 rule checks, each run five times.
| With Jaxon | Without Jaxon (best result per approach) | ||||
|---|---|---|---|---|---|
| Metric | DSAIL + Claude Opus 5.5 | DSAIL + GPT 5.6 Sol | Best careful prompting | Best RAG | Best LLM-as-judge |
| Correctness | 100% | 100% | 78.5% | 73.8% | 78% |
| Auditability | ✔Yes | ✔Yes | ✕No | ✕No | ✕No |
The benchmark checked written adjudication rules against background reports; eDiscovery protocols are different documents, and we do not claim the numbers carry over. A pilot on your own protocol is how you find out. Full methodology and results
Six AI verification use cases for legal teams.
Privilege log validation & AI privilege calls
Privilege logs are where review protocols meet opposing counsel. AI review tools now flag privilege at first pass, which speeds the work but does not show that the protocol was applied the same way to every entry. Jaxon encodes your privilege protocol and the ESI order as formal DSAIL® rules, extracts the facts each rule needs with the model you approve, and checks every log entry and every AI privilege flag before the log is served.
- ▪Required fields checked on every entry: author, recipients, date, and a stated privilege basis.
- ▪Attorney-on-communication rule checked against the matter's attorney list, with the names and the lines they came from.
- ▪Third parties on a thread flagged before a privilege claim is served.
- ▪AI privilege flags from your review platform checked against the same rules as human calls.
- ▪A blank or unreadable recipient field returns UNKNOWN, never a guessed TRUE.
- ▪Per-entry record: rule applied, protocol text, facts extracted, cited passage, ruleset version.
Production QC before it leaves the firm
A production has to match the ESI protocol and the protective order. A defect found after service means a clawback request, a re-production, or a dispute over whether the error waived anything. Jaxon encodes the production specifications as rules and checks the production set and its load files before they go out, so defects are caught at the firm rather than by the other side.
- ▪Required metadata fields present and populated for every document in the set.
- ▪Confidentiality designations checked against the protective order's criteria.
- ▪Redactions verified wherever the protocol requires them.
- ▪Bates numbering checked for gaps, overlaps, and the agreed prefix and format.
- ▪Natives, images, text, and load files checked against the ESI protocol's format specifications.
- ▪A pre-production record of every check, ready if the production is challenged.
Review protocol consistency across AI and human reviewers
A review coding protocol sets objective criteria. Large review teams apply those criteria differently, and AI first-pass review applies them by probability. Quality control samples a fraction of the work. Jaxon checks every coding decision, AI or human, against the protocol's objective criteria, so inconsistencies are found across the whole set rather than in a sample.
- ▪Responsive calls checked against the agreed custodians and date range.
- ▪Issue codes checked against the protocol's defined issues.
- ▪Same facts, same ruleset, same result across reviewers, batches, and vendors.
- ▪AI first-pass coding checked with the same rules applied to human reviewers.
- ▪Inconsistent calls surfaced with the rule, the fact, and the passage behind them.
- ▪Whole-set coverage of objective criteria instead of statistical sampling.
Court filings, local rules & citations
Courts are sanctioning filings that cite cases that do not exist, and many judges now issue standing orders on AI-assisted filings. Jaxon encodes the applicable court rules and your firm's citation standards, then checks every brief before filing.
- ▪Each cited authority checked against the citator or research source you designate. A citation that can't be found returns FALSE.
- ▪Pin cites and subsequent-history checks required by your citation rules.
- ▪Page and word limits, formatting, and required sections checked per court.
- ▪Standing-order requirements on AI-assisted filings encoded per judge.
- ▪Deadlines computed from service under the applicable rules.
- ▪A pre-filing record of every check, tied to the version of the brief that was filed.
Outside counsel guidelines & billing
Every corporate client has written billing rules. Invoices that break them are cut or rejected in the client's e-billing system, often long after the work is done. Jaxon encodes each client's outside counsel guidelines and checks every time entry and invoice before it goes out, so write-downs stop at the firm rather than at the client.
- ▪Each client's guidelines encoded once and applied to every time entry.
- ▪Block billing, vague descriptions, and non-billable categories flagged before submission.
- ▪Rates and timekeeper levels checked against the client's approved rate agreement.
- ▪UTBMS task and activity codes checked for presence and fit.
- ▪Staffing limits, such as attendees per meeting or timekeepers per task, enforced as rules.
- ▪A pre-submission record per invoice, for the billing partner and the client.
Firm AI-use policy & governance
ABA Formal Opinion 512 sets out what the ethics rules require when lawyers use generative AI: competence, confidentiality, client communication, supervision, and reasonable fees. Clients and insurers are starting to ask firms to show how they meet it. Jaxon encodes your firm's written AI policy and checks each matter's AI usage against it, producing a record you can share.
- ▪Approved-tool lists enforced per matter and per client.
- ▪Client consent and disclosure requirements checked before AI is used on a matter.
- ▪Rules on what may not go into a model, checked on every use.
- ▪Client-specific AI terms from engagement letters and guidelines encoded per client.
- ▪Diligence checklists and deal-document defined terms checked for consistency.
- ▪A firm-wide record of AI usage, exceptions, and remediations.
How Jaxon verifies an AI output: POST, check, verdict, log.
Any LLM: a privilege call, a coding decision, a cited authority.
Formal check against your encoded, version-controlled rulebook, run by a symbolic solver.
Where must your client data stay?
Fastest to production
Most isolated
Constraint
No client-confidential data
Deployment 01
SaaS / managed cloud
Fastest time to production. Isolated, encrypted execution, suited to firm-internal rules testing and non-confidential workflows. Available via AWS Marketplace.
Constraint
Must stay in your cloud
Deployment 02
Your cloud tenant
Recommended
Deployed inside your own Azure, AWS, or Google Cloud environment, using the model you approve. Recommended for client-confidential matter data.
Constraint
Must stay in your perimeter
Deployment 03
On-premises
Deployed on your own infrastructure. No data leaves your perimeter, and there are no external API dependencies.
Constraint
No external connectivity
Deployment 04
Air-gapped
Fully disconnected, for the most sensitive matters. Backed by Jaxon's federal heritage in mission-critical disconnected environments.
Ready to put verified AI into your discovery, filing, and billing workflows?
Jaxon's engineering team works directly with your discovery counsel, litigation support, knowledge management, and information security teams to encode your protocols and stand up verification inside your environment. Most firms start with a six-to-eight-week pilot on a closed or sanitized matter.
Your protocols. Your environment. A verdict you can produce.
The form could not load in this browser. You can still reach the team directly.
Email the teamOr write directly: info@jaxon.ai
Does Jaxon replace attorney review or give legal advice?
No. Jaxon checks documents, log entries, coding decisions, filings, and invoices against the rules your attorneys approve and returns TRUE, FALSE, or UNKNOWN for every rule, with the trace behind it. The professional judgment stays with your lawyers. Jaxon gives them a consistent, reproducible record behind each call.
Does it work with our review platform?
Yes. Your review platform stays the system of record for collection, processing, review, and production. A pilot runs on exports, so it needs no integration and no access to your review environment. In production, the same checks run on scheduled exports or through the platform's APIs, with results returned as a report or written back where the platform supports it.
Where does client data go?
Nowhere new. Jaxon deploys in your own cloud tenant or on your own infrastructure, and extraction runs on the language model your firm configures with its own credentials. Jaxon does not host, store, or process client data, and document content never appears in audit or operational logs.
What if a document is missing information?
The rule returns UNKNOWN and names the missing fact. Nothing is guessed, and UNKNOWN is never counted as TRUE. Your workflow decides how each UNKNOWN is handled: routed to a reviewer, held, or escalated. Either way, the record shows the rule was run.
How does a pilot work?
A pilot takes about six to eight weeks. In the first two weeks we encode one protocol, such as a privilege protocol, and your protocol owner approves every rule. We then run it against an export from a closed or sanitized matter, walk through the FALSE and UNKNOWN results with your team, and confirm that replaying the stored facts reproduces every result exactly.
Do your benchmark results apply to legal documents?
Not automatically. DSAIL Benchmark 3.0 checked written adjudication rules against background reports, and eDiscovery protocols are different documents. What carries over is the architecture: the model answers narrow questions of fact, and deterministic logic decides the verdict. A pilot on your own protocol is how you measure it.