Lunch and learn | Salt Lake City law office

AI in Legal Practice

What to Try, What to Question, What to Verify

Sam Rogers, Snap Synapse & PAICE.work PBC

Presented November 4, 2026. A record of that day, not updated since. Not legal advice.

Lawyers around a conference table with laptops and a screen
AI-generated illustration
Quick show of hands

Who's in the room

  1. Used an AI tool this week?
  2. Used one for client work?
  3. Ever got an answer you didn't trust, or later found was wrong?
An attorney working at a laptop in an office
AI-generated illustration
One more hand

What worries you more about AI at work?

Five panels of a city skyline, from theoretical to consuming worry

AI-generated illustration

That it replaces what we do

That it's confidently wrong in something we sign

Who's talking

Sam Rogers

  • Founder, Snap Synapse. I help people ask AI better questions, judge what comes back, and keep their own judgment in charge.
  • PAICE.work PBC: the Legal Graph connects AI laws, obligations and incidents. So I read what AI gets wrong about law, and what courts do about it.
  • Past expert witness work. Current research: AI collaboration, what I call Aggregated Intelligence.
  • Not a lawyer. Nothing today is legal advice.
Sam Rogers
Why I'm here

No pitch today.

  • A Salt Lake City law office made this happen, and I'm grateful.
  • Nothing for sale here, no sign-up sheet, and the same four checks apply to every tool on these slides.
  • What I get out of it: your questions, in your words. They shape what I teach next.
?

By the end: one thing to try, and one check to run.

The card is for the question you'd rather not ask out loud, or the one thing about AI at work that worries you. No names, no client details. I'll collect them before the questions.

The four checks panel: every source the answer cites, with opened and still-good boxes left for you to fill
What to question

Wrong answers look exactly like right ones.

A lawyer reading a polished document on a tablet beside stacked papers
AI-generated illustration
Demo

A narrow Utah question

 A general chatbot

Asked of a general chatbot, the way most people use one.

Testing record: CJ-TR-20261104, ¶¶4–8; Exs. CJ-CL-A1–A3. All 30 runs are indexed in the appendix.

Saved run |

What came back, and what we found

The answer, as given“Why the defense fails: Rule 40 is the appellate counterpart to Civil Rule 11. Your signature certifies the filing, so who drafted it is irrelevant. The court also cited Utah RPC 3.3, which bars a lawyer from knowingly or recklessly making a false statement of fact or law to a tribunal. Signing unchecked citations is the reckless part. And under RPC 5.3, a lawyer supervising nonlawyer staff is responsible for their work […]”
Garner opinion, page 5 footnote 4, rendered from the saved PDF

Garner, page 5 footnote 4, rendered from the opinion. The court expressly declines to find the intent Rule 3.3 requires. Real case; misread source.

Verbatim excerpt, retypeset; the ellipsis marks where it continues. CJ-TR-20261104, ¶9; Ex. CJ-CL-A1, L020 (capture); Garner, ¶10 n.4.

2023 court record | Southern District of New York

Does reassurance count as evidence?Seal of the United States District Court for the Southern District of New York

The lawyer asked ChatGPT whether the cases were real. It said they were.

Filed with the court in Mata v. Avianca. This is a 2023 record, not a fresh model run.

What independent source would show that a case exists, and says what we need?

Appendix: case-treatment review · sources.

Appendix B, page 43 of the Mata sanctions order: asked whether the cases are fake, ChatGPT assures the user they are real

Mata v. Avianca, S.D.N.Y. 22-cv-1461, ECF 54, p. 43 (June 22, 2023). Rotated for reading.

Utah Court of Appeals | May 22, 2025

It happened here.Flag of Utah

  • Garner v. Kadince, 2025 UT App 80
  • A petition cited cases that don't exist. An unlicensed law clerk drafted it with ChatGPT.
  • Sanctions: the other side's fees, a refund to the client, and a $1,000 donation to "and Justice for all".
  • Counsel admitted it and took responsibility.

The signal: it's still happening here. In September 2026, the federal court in Utah sanctioned two more lawyers. Courts elsewhere now cite Garner.

Appendix: case-treatment review · sources.

Page 7 of Garner v. Kadince, the conclusion ordering three sanctions

2025 UT App 80, p. 7, conclusion.

What we just saw

Three ways a confident answer goes wrong

  1. The source doesn't exist.
  2. The source doesn't say that.
  3. It said that once, and the law has moved.
ABeus Gilbert PLLC v. Brigham Young UniversityNo. 2:12-cv-00970-TS, ECF 385 (D. Utah Sept. 9, 2026)
BVarghese v. China Southern Airlines Co., Ltd.925 F.3d 1339 (11th Cir. 2019)
One of these is real. Which one?
What to try

Same tool.
Ask differently.

Illustration of AI as a tool, an assistant and a partner
AI-generated illustration
Demo | worth a photo

Ask for evidence, not just an answer

1 Jurisdiction2 Dates3 Quote and pinpoint4 Say so if not found
 A general chatbot

CJ-TR-20261104, ¶¶6–8, 13; Exs. CJ-CL-P1–P3. Evidence instructions were tested as one bundle.

Saved run |

What came back this time

Asked for quotes and pinpoints“No Rule 3.3 finding. In n.4 (attached to ¶10), the court found that counsel made a false statement of law, but “we find that their conduct fell short of the level of intent required by the rule.” Rule 3.3 requires that the false statement be made knowingly or recklessly.”
Garner page 5 footnote 4, checked against the saved PDF

The quoted passage, checked in the opinion. Same footnote as the last run; this time the answer quotes it and gets the distinction right.

Verbatim excerpt, retypeset. CJ-TR-20261104, ¶9; Ex. CJ-CL-P1, L042 (capture); Garner, ¶10 n.4.

Everyday work | Saved, source-bound example

A chronology we can check

Public opinion supplied. Three referenced rows returned. Every row checked.

EventDateSource in the opinion
Petition for interlocutory appeal filedNot statedPDF p. 2, ¶2
Order-to-show-cause hearingApril 22, 2025PDF p. 1, ¶1; PDF p. 3, ¶4
This opinion filedMay 22, 2025PDF p. 1, caption (no paragraph number)
“On April 22, 2025, Petitioner’s counsel appeared at the OSC hearing along with Petitioner.”

Open Garner, PDF p. 3, ¶4. The petition's filing date stays “Not stated.”

Saved Claude table, retypeset without changing its cells. Opus 5.5 Medium, November 4, 2026. Ex. CJ-DOC-01; CJ-TR-20261104, ¶¶21–24; source opinion (see testing record materials).

What to give it, what to keep out

Before anything goes in

Give it

  • The document, if it's cleared to share
  • The jurisdiction
  • The date or time window
  • The task, and the form you want back: quotes and pinpoints

Keep out

  • Client information, until the firm has:
    • approved the tool and the workflow
    • checked data handling and security
    • any client consent required
  • A local model needs the same checks
Question and document A vendor's cloud Your own hardware The firm's checks An answer you'd sign

Running it locally changes who could see the data. It doesn't replace the firm's checks, or yours.

Where the data settings live

Consumer account or firm account?

Claude Max
Settings → Privacy → Help improve our AI models
“Allow the use of your chats and coding sessions to train and improve Anthropic AI models.”
Off in this account
ChatGPT Pro
Settings → Data controls → Improve the model for everyone
Off in this account

These are training controls. Retention, access and the firm's approval are separate checks. Setting names as captured November 4, 2026; vendors rename them.

CJ-TR-20261104, examination CJ-QA-05. Captures: Claude, ChatGPT, 2026-11-04; retypeset for the screen, no settings changed.

What to verify
[E]verything must be reviewed, verified, and quality-controlled by a licensed attorney.
Utah State Bar, "AI Tools Utah Lawyers Can Use Today," January 15, 2026

Appendix: sources, with the Bar's post linked.

Someone reading an open book beside a laptop
AI-generated illustration
Check 1 of 4

Open it.

Does each cited source exist? Pull it up yourself, not from the AI's link text.

Appendix: sources.

Page 1 of the Mata sanctions order, with caption and filing header

Worked example: Mata v. Avianca, ECF 54, p. 1. Check the caption, docket, date and document number.

Check 2 of 4

Read it.

Does the pinpoint actually say what the answer claims?

Remember the tool vouching for itself: that isn't a reading. Only the opinion can tell you.

Someone checking a printed book against a tablet
AI-generated illustration
Check 3 of 4

Date it.

Is it still good law, the current version, the right jurisdiction?

Appendix: case-treatment review, what was checked for this deck and its limits.

Excerpt of page 19 of the Mata order, findings 45 and 46 about the ChatGPT screenshots

Worked example: Mata, ECF 54, p. 19, findings 45-46 (excerpt). A 2023 federal order doesn't establish current model performance or controlling Utah law.

Check 4 of 4

Own it.

Would you sign it? If not, it's a lead, not an answer.

Everything that I do, I gotta own. I am accountable for that.
Michael SimonMichael SimonAttorney and owner, Law Plus Data LLC
Chief Strategy Officer, Bells Up AI
October 2026
Excerpt of page 34 of the Mata order, conclusion paragraphs b to d: letters to each falsely named judge and a $5,000 penalty

Worked example: Mata, ECF 54, p. 34, conclusion (b)-(d) (excerpt). After a finding of bad faith: letters to the client and each judge falsely named, and a $5,000 penalty, joint and several.

Legal authority: Mata, ECF 54, pp.1–2, 34. Curated research trail and its limits: Legal Graph appendix.

Quick pass

Same four checks, asked differently

Asked for an answer“[…] The court also cited Utah RPC 3.3, which bars a lawyer from knowingly or recklessly making a false statement of fact or law to a tribunal. Signing unchecked citations is the reckless part. And under RPC 5.3, a lawyer supervising nonlawyer staff is responsible for their work, so “my clerk did it without my knowledge” is less a defense than an admission of a supervision failure. […]”
Asked for evidence“No Rule 3.3 finding. In n.4 (attached to ¶10), the court found that counsel made a false statement of law, but “we find that their conduct fell short of the level of intent required by the rule.” Rule 3.3 requires that the false statement be made knowingly or recklessly.”

Verbatim excerpts of the saved answers, retypeset; ellipses mark omitted text. CJ-TR-20261104, ¶¶9–18; Ex. CJ-CL-A1, L020 and Ex. CJ-CL-P1, L042. Selected excerpts; full sample retained.

What would you hand this to first?

A task you do every week. In your own words.

A desk stacked with binders and files
AI-generated illustration
?

Question cards, please.

Pass them to me. No names, no client details. I'll read some aloud now, and every one later.

Pausing for Questions

What's your first question?

Three fact patterns

  1. An associate pastes a client's deposition transcript into a free chatbot to get a summary.
  2. Opposing counsel's brief cites a case you can't find anywhere. What do you do next?
  3. An AI-drafted brief comes back with five citations. You have ten minutes before filing. Which check do you skip, if any?
A busy office with a clock on the wall
AI-generated illustration
Hands up if you agree

Agree or disagree?

  1. “Every office should have a written AI policy by the end of this year.”
  2. “If AI helped draft it, the court should be told.”
  3. “I'd trust an AI summary of a document I haven't read.”
Same question, one more time

What worries you more about AI at work?

Five panels of a city skyline, from theoretical to consuming worry

AI-generated illustration

That it replaces what we do

That it's confidently wrong in something we sign

One thing to try this week

Stop asking the tool if it's sure.
Ask for the quote and the pinpoint, then open it.

Open it.Read it.Date it.Own it.

Thank you.

QR code for https://snapsynapse.com/legal-ai/

Four checks and sources:
https://snapsynapse.com/legal-ai/

That's the session. Anyone who needs to go can go. I'm staying for questions.

Prepared with AI assistance (Claude, Codex, Perplexity). Each factual claim was logged with its source and how it was checked.

Appendix: sources · testing record · how this deck was made.

Appendix | How this deck was made · 1 of 3

Handoffs in the chain: who checks each handoffChecked like we'd check anything else

WhenFrom → toWhat was handed overWhat gated it
Sep 14Sam, with CodexInvitation copy and the promises this deck is checked against.Sam confirmed the description before it went out.
Oct 18Sam → ClaudeFirst run of show. Sam picked the demos.Sam's choices, recorded in the vault note.
Nov 3Claude → deckOne offline page, 27 slides, plus a claims register: every checkable claim with a status and a source.Script syntax, unique ids, every local link resolves.
Nov 3Claude → CodexThe deck, by SHA-256, the run of show and the kit. Codex wrote its verdict before reading the author's own.Five ranked findings, each with a line number. Only the findings file was written.
Nov 3Codex → Claude, at Sam's goCorrections applied; declined items named with the reason.Each change logged against a register row.
Nov 3Sam → Perplexity → ClaudeFive searches written to find contradictions. Claude opened every cited source.No row changed without Sam's decision. Differences recorded, not fixed silently.
Nov 4Codex → test record30 paired runs in five systems, one checked chronology, memorandum CJ-TR-20261104 with exhibits and hashes, eleven examinations.Preflight exit 0; every slide checked at native size; a written handoff for the next model.
Nov 4Sam → Claude Fable 5.1 → Claude Sonnet 5.532 numbered slide notes; design pass v1.4; then a read-only audit by a second model.Preflight exit 0; quotes verbatim against the exhibits; every link resolves; CJ-QA-12.
Nov 4Claude → SamTimed rehearsal, printing, HDMI, the talk itself.Still Sam's. No model can rehearse for him.

Records: run of show and claims register notes, CJ-TR-20261104, CJ-QA-12, `review/codex-evaluation-2026-11-03.md`. Versions given where the record names them; otherwise the product name stands.

Appendix | How this deck was made · 2 of 3

What the checking caught

Between models

  • Codex: the first keep-out rule read as permission. Under Rule 1.6, a license or owned hardware isn't an exception.
  • Codex: the slide meant to show a $5,000 sanction had cropped it out of view.
  • Codex: a note called a model "released today"; its own posts were dated October 2026.
  • Claude: a prep-kit preview labeled a newspaper the "primary source" for a court case. Cut.
  • Claude: Codex flagged "courts elsewhere cite Garner" as unverified; opening both later opinions confirmed it, so it stayed.
  • A script: Claude's own chat summary of the register miscounted three status totals.

On the day

  • Codex: two of three plain Claude answers misread Garner's footnote 4. Real case, wrong intent finding. That became the demo.
  • Sam: the saved-run crops were 63 to 148 pixels tall, unreadable on a projector. Retypeset verbatim, exhibit cited, crops kept and linked.
  • Sam: the real case on the real-or-fake card was the one the previous slide had just named. Swapped for Beus Gilbert.
  • Claude Sonnet 5.5, auditing Fable 5.1: every retypeset quote matched its exhibit; one AI illustration had no label. Labeled.
Third pass, Perplexity, run by Sam: five searches looking for contradictions found none. One new Utah sanction (Beus Gilbert v. BYU, D. Utah, September 2026), confirmed in the court's own docket. Of 107 sources returned, at least 13 were unrelated keyword matches. A citation in a list isn't support.

The register distinguishes primary sources, issuers' pages, my own facts, demo-dependent claims and open questions. Test record and other examinations: CJ-TR-20261104, §§1–7.

Appendix | How this deck was made · 3 of 3

Every handoff carries an artifact and a check

Sam decides at every handoff. No slide and no register row changes automatically. deck + SHA-256findings fileregister handoff note, kit test recorddeck + 32 notesaudit, CJ-QA-12 Build Review Correct Search to contradict Test and record Design Audit Rehearse, present Claude: deck and claims registerNov 3 Codex: verdict written first,five ranked findingsNov 3 Claude, at Sam's go: each fixlogged to a register rowNov 3 Perplexity, run by Sam; everycited source opened by ClaudeNov 3 Codex: 30 paired runs, five systems,memorandum CJ-TR-20261104, hashesNov 4 Claude Fable 5.1: Sam's 32 notes,design pass v1.4, preflight 0Nov 4 Claude Sonnet 5.5, read-only:quotes verbatim, links resolveNov 4 Sam: timed run, print, HDMI,the room's questionsNov 4, pending Each arrow carries three things A named artifact (a file, a hash, a note) · a check anyone can rerun (preflight exit 0, a script, the source opened) · a stated home for the state (a vault note, review/, test-record/) Author and checker are different models where the stakes justify it. Same four checks: open it, read it, date it, own it.

Drawn from the records on the previous two slides. Editable source: `review/deck-workflow-2026-11-04.mmd` (Mermaid). Dark boxes outline the builder, grey the checker.

Appendix

Sources

AI Demonstration Testing Record, CJ-TR-20261104 (2026-11-04), numbered memorandum and complete exhibit schedule. Open full record. Case treatment · Legal Graph citations and limits.

Appendix | Testing record · CJ-TR-20261104

Testing memorandum and exhibits

AI Demonstration Testing Record, CJ-TR-20261104
November 4, 2026 · Version 1.3 · Prepared for Sam Rogers

Open the full numbered memorandum and exhibits

T opens this index. Arrow keys tour the appendix; Escape returns to the main slide.

Appendix | Testing record · CJ-TR-20261104

Instructions, materials and method

Three plain and three structured responses per accessible system. Every actual answer retained; none regenerated to obtain a desired result.

Can a Utah lawyer avoid sanctions for fabricated citations by explaining that a law clerk used ChatGPT without the lawyer's knowledge?

Structured condition added Utah state courts, 2023 to November 4, 2026, full citations, quoted support with pinpoints, and permission to report no verified case.

Materials: original records, selected captures, court opinions, rule text and the claims register. The complete prompts appear in every exhibit.

CJ-TR-20261104, ¶¶3–8. Findings are proposition-specific, not complete legal clearance.

Appendix | Testing record · CJ-TR-20261104

Conditions of examination

SystemObserved modeSearch / material limitation
ClaudeOpus 5.5 MediumVisible web search
ChatGPTA1 Instant; remaining runs MediumAll responses said web search unavailable
GeminiFlash HighVisible web search
CopilotAuto; backend model unidentifiedVisible search/source results
Qwenqwen3.8:latest; 27.3B Q4_K_M; medium thinkingNo web search tools

Perplexity: zero paired-test runs, access blocked. Account memory was not disabled. Copilot A2/A3 shared a conversation URL.

CJ-TR-20261104, ¶¶7, 13–17. Browser timestamps are captures; Qwen timestamps are invocation starts. Exhibit times are UTC and MST.

Appendix | Testing record · CJ-TR-20261104

Claude: complete run schedule

Opus 5.5 Medium · Visible web search

ExhibitUTC timeRecorded observation
CJ-CL-A112:23:10Garner found; Rule 3.3 intent misread.
CJ-CL-A212:25:29Same Rule 3.3 recklessness assertion.
CJ-CL-A312:27:12Rule 40 outcome described; Rule 5.3 added analysis.
CJ-CL-P112:34:10Footnote 4 intent distinction quoted correctly.
CJ-CL-P212:39:06Intent distinction recognized; footnote paragraph off.
CJ-CL-P312:41:56Intent distinction and footnote locator recognized.

CJ-TR-20261104, §6. Click an exhibit for the exact prompt, complete transcript, line references and hashes. A narrow observation is not approval of every assertion.

Appendix | Testing record · CJ-TR-20261104

ChatGPT: complete run schedule

A1 Instant; remaining runs Medium · All responses said web search unavailable

ExhibitUTC timeRecorded observation
CJ-CG-A112:33:00General rule analysis; no verified Utah case.
CJ-CG-A212:36:41Mata discussed; live search unavailable.
CJ-CG-A312:40:11Mata discussed; live search unavailable.
CJ-CG-P112:42:43Declines a verified Utah case/quote.
CJ-CG-P212:46:11Declines verified support for either categorical answer.
CJ-CG-P312:49:16Declines a verified Utah case/quote.

CJ-TR-20261104, §6. Click an exhibit for the exact prompt, complete transcript, line references and hashes. A narrow observation is not approval of every assertion.

Appendix | Testing record · CJ-TR-20261104

Gemini: complete run schedule

Flash High · Visible web search

ExhibitUTC timeRecorded observation
CJ-GM-A112:33:30Garner found; added disciplinary claim unsupported.
CJ-GM-A212:37:27Garner found; no exhaustive grading of all claims.
CJ-GM-A312:42:04Garner found; broader assertions not fully graded.
CJ-GM-P112:44:32Paragraph 8 paraphrase put in quotation marks.
CJ-GM-P212:46:25Paragraph 7 source wrongly attributed to Mata.
CJ-GM-P312:50:25Same attribution error; paragraph 10 text stitched.

CJ-TR-20261104, §6. Click an exhibit for the exact prompt, complete transcript, line references and hashes. A narrow observation is not approval of every assertion.

Appendix | Testing record · CJ-TR-20261104

Copilot: complete run schedule

Auto; backend model unidentified · Visible search/source results

ExhibitUTC timeRecorded observation
CJ-CP-A112:38:19Garner found; central outcome described.
CJ-CP-A212:40:27Garner found; same URL later used for A3.
CJ-CP-A312:43:16Garner found; same URL as A2.
CJ-CP-P112:47:22Central Garner quotations checked against opinion.
CJ-CP-P212:50:34Central Garner quotations checked against opinion.
CJ-CP-P312:55:10Central Garner quotations checked against opinion.

CJ-TR-20261104, §6. Click an exhibit for the exact prompt, complete transcript, line references and hashes. A narrow observation is not approval of every assertion.

Appendix | Testing record · CJ-TR-20261104

Qwen: complete run schedule

qwen3.8:latest; 27.3B Q4_K_M; medium thinking · No web search tools

ExhibitUTC timeRecorded observation
CJ-QW-A112:49:48No named case; broad rule assertions unapproved.
CJ-QW-A212:54:48No named case; broad rule assertions unapproved.
CJ-QW-A312:58:38Mata mentioned; general assertions unapproved.
CJ-QW-P113:03:33No verified matching Utah case supplied.
CJ-QW-P213:05:36No verified Utah case; surrounding rules unapproved.
CJ-QW-P313:08:59No verified Utah case; false Rule 8.4(b) quotation.

CJ-TR-20261104, §6. Click an exhibit for the exact prompt, complete transcript, line references and hashes. A narrow observation is not approval of every assertion.

Appendix | Testing record · CJ-TR-20261104

Limits of the observations

CJ-TR-20261104, ¶¶13–18. Observations and interpretations remain distinct from the verbatim exhibits.

Appendix | Testing record · CJ-TR-20261104

Other examinations and prior reviews

ReferenceExamination / recordScope
CJ-QA-01–04Preflight, script, layout, cards/QRTechnical and session checks
CJ-QA-05 / 06Settings / source chart and linksBounded inspection
CJ-QA-07Source-bound chronologyThree rows and quotation checked
CJ-QA-08 / 09Graph citations / v1.2 validationSource roles, snapshots, layout
CJ-QA-10 / 11Case treatment / full-slide auditPublic review limits; all remaining slides
CJ-REV-01Independent Codex deck reviewNovember 3, 2026 evaluation
CJ-REV-02Earlier Perplexity review by SamAttributed; raw exports not inventoried
CJ-ACCESS-PPPaired-test Perplexity accessZero responses; access outcome only

CJ-TR-20261104, §§7, 11–13: examination records. These are separate from the 30 model responses.

Appendix | Testing record · CJ-TR-20261104

Citation and exhibit references

AI Demonstration Testing Record, CJ-TR-20261104 (Nov. 4, 2026), ¶9, Ex. CJ-CL-A1, L020.

Open the memorandum · Open the structured inventory

What's out there | as of November 2026

Tools you'll hear about

  • Lexis+ AI: announced in a January 2026 Utah State Bar post as the Bar's AI partner, with a licensee discount
  • Westlaw's AI tools, and business versions of general assistants (ChatGPT, Claude, Copilot)
  • AI doesn't have to mean cloud: open-weight models can run entirely on your own hardware. Z.ai, for one, publishes open-weight GLM models.
  • Enterprise legal AI for large firms

No endorsement. Check current access and data terms before client material goes in. The four checks apply to every one of them.

Z.ai legal benchmark chart comparing GLM-Legal, GLM-5.3-Flash, Kimi K3, Claude Fable 5 and GPT-6 Astra on three legal benchmarks
Vendor-reported by Z.ai, which makes GLM-Legal. Not independently reproduced. Source: docs.z.ai, GLM-5.3-Flash guide.
Appendix | Testing record · CJ-TR-20261104, v1.3

Additional document-task example

Ex. CJ-DOC-01: one saved Claude chronology trial using all seven pages of the public Garner opinion as text.

Separate from the original 30 paired runs. This demonstrates one checked extraction, not a comparative time or accuracy benefit.

Full prompt and output, CJ-DOC-01 · Record ¶¶21–22 · Source checks, CJ-QA-07

Appendix | Testing record · CJ-TR-20261104, v1.3

Conclusions from the saved runs

CJ-TR-20261104, ¶¶23–24; bases in ¶¶9–18 and Ex. CJ-DOC-01. No general accuracy rate or measured time saving.

Related framework: EveryAILaw, Human Oversight (editorial category, not a case-specific legal duty). Evidence trail and limits.

Appendix | Testing record · CJ-TR-20261104, v1.3

Hypothesis for the next test

H1, not comparatively tested: evidence instructions and supplied-source analysis will reduce unsupported material claims and human verification burden while preserving important qualifications.

  1. A: ordinary realistic research assignment.
  2. B: the same assignment, with primary-source support, exact quotes, pinpoints and explicit gaps.
  3. C: corresponding analysis using the supplied opinion only.

Keep system conditions fixed. Compare common interpretation claims; assess discovery coverage separately for A/B. One successful chronology extraction does not establish H1.

CJ-TR-20261104, ¶¶25–28. The proposed comparative batch has not been run.

Appendix | Testing record · CJ-TR-20261104, v1.3

Proposed seed and evaluation

Hypothetical: In a Utah state appeal, a lawyer signs a petition containing invented case citations. An unlicensed clerk used ChatGPT without the lawyer's knowledge. A second lawyer is counsel of record but neither drafted nor signed the petition. Prepare a 250-word research note for counsel responding to the court's order to show cause. Identify the most relevant Utah state decisions, arguments that could limit each lawyer's exposure, adverse authority, and remedies the cases actually imposed.

Choose four to six tasks and source-based answer keys before running. Retain every output.

Measure material-claim correctness, source support, quote/pinpoint fidelity, omitted qualifications, justified abstention, human checking time and substantial corrections. More errors, omissions or checking burden count against H1.

CJ-TR-20261104, ¶¶26–28. Qualified legal review where judgment is required.

Appendix | Public-source review · November 4, 2026

Case-treatment review

CaseHistory or later treatment foundUse in this deck
GarnerWhiting and TOV/Kosel cite it in 2026. Rule 40 / RPC 3.3 distinction preserved.Historical Utah example.
MataLater cited by Whiting and Beus Gilbert. ECF 55 separately dismisses the claim as untimely.2023 record; bad-faith qualification.
Beus GilbertSept 14 ECF 386 concerns the arbitration merits, not vacatur of Sept 9 sanctions.Dated sanctions order.
LaceySpecial-master order; later settlement and Sept 18, 2025 dismissal with prejudice.Context only; reviewed dismissal does not address sanctions.
PrisbreyWatson cites its briefing standards in August 2026. No AI-use finding in Prisbrey.Excluded as AI-sanctions evidence.
WadsworthWhiting cites it; Garner ¶7 is the source of the attribution check.Context and quotation attribution.

No adverse disposition located that changes the narrow propositions used. Public docket and certiorari-index coverage is incomplete; no commercial citator clearance is claimed.

Full eight-case review, dates, source locators and limits · CJ-TR-20261104, §12. Raw model responses remain unchanged.