Using AI Safely on a Case

The tool drafts. Your judgment governs.

AI is fast and fluent, and fluency is not accuracy. A confident, well-formatted answer can still contain a fabricated case, a wrong deadline, or a "fact" that isn't in the record. Every skill here is built around that reality — and so should your habits be.

Treat every AI output as a lead, never a source. The signature on the filing is yours, not the model's.
01

Output is a lead, not a source

Every date, citation, and factual assertion routes back to the underlying record or authority before it leaves your office.

02

Demonstrate the failure once

Watch a confident answer collapse under verification, and the verification habit sticks for good.

03

Guard what you paste

Be deliberate about which client facts enter any tool. Confidentiality is a decision you make on every prompt.

04

The signature is yours

The skill drafts and flags its assumptions. You verify, you decide, you sign. That step is never delegated.

Two duties to keep front of mind. Confidentiality — be deliberate about what client information goes into any tool. Candor and competence — you remain responsible for every fact and citation that leaves your office, exactly as if you'd written it yourself.
We hold the skills to the same standard. As of v0.2.0 every legal proposition in this library is pin-cited to the subsection and dated in mo-dwi-authority.md, verified against the Revisor and CourtListener rather than against memory. Propositions we could not verify are marked OPEN and the skills will not assert them. The method, the four substantive defects v0.2.0 fixed, and the eleven errors we made finding them are all published at /verification-protocol. A library that tells you to check its work should show you its own.