matematicsolutions/patron

> A local-first, self-hosted AI workspace for a law firm. A single-user desktop
> application (Electron) that keeps case files on the machine it runs on: local SQLite by default (ADR-0053), 20 bundled connectors to Polish, EU and national law
> (SAOS / NSA / ISAP / KRS / EUREKA / EUR-Lex / EU-Compliance), a hash-chained audit trail,
> bring-your-own-model (a local Ollama model, or Gemini / Claude / OpenRouter with your own key). A server mode (Postgres + MinIO) remains available as an alternative.
Patron is a fork of Mike (a document-centric
legal assistant, AGPL-3.0). The Patron shell inherits AGPL-3.0 as a derivative
work. It adds Polish localization, a Polish legal stack, and the compliance
requirements a law firm needs. The full rules live in
governance/CONSTITUTION.md.
## What Patron does
Everything below ran end-to-end on 2026-08-23 against a real model on synthetic contract fixtures
(npm run smoke:surfaces, smoke:desktop, packaged app e2e:smoke); nothing here is a roadmap item.
Chat over the case files with a colour badge next to every citation from your own documents:
green (verbatim), yellow (paraphrase), red (the source does not support the claim). A local
paraphrase judge, never a cloud call, decides the colour.
Case law, legislation and tax practice while answering - 20 MCP connectors ship in the
installer: 7 for Polish and EU sources (SAOS, NSA, ISAP, KRS, EUREKA, EUR-Lex/CJEU) queried live,
plus 13 national ELI connectors (DE, FR, IT, ES, NL, SE, AT, FI, IE, LU, BR, GB, US) that follow
the European Legislation Identifier. On top of that an offline EU compliance corpus (GDPR, AI Act,
DORA, NIS2, eIDAS 2.0, CRA) that works without internet. Connector answers carry source, signature or
identifier, date and URL (measured on SAOS and EUREKA; the same MCS contract applies to the rest).
A table from a batch of contracts (Tabular Review): you define the columns as questions,
Patron fills one cell per document with the answer, a quote from the source page and a
confidence flag (green / yellow / red / grey).
Editing documents as a lawyer does - you ask for a change and review it as Word tracked
changes, then accept or reject. A file edited in Word comes back into Patron with its changes
intact.
Drafting - generate a new .docx from the chat, or run a whole pleading through a review,
devil's advocate and language pass before it leaves the firm.
Workflows - saved prompts and column sets you reuse across cases.
Human-in-the-loop for agent writes (on by default, ADR-0137; PATRON_MUTATION_APPROVAL=false
switches it off): edits, generated files, copies, comments and memory writes are staged as
approval cards; nothing is written until a human approves.
An audit trail a third party can verify - every model interaction hash-chained with a Merkle
root, built for record-keeping duties such as AI Act art. 12 where they apply; exportable as a ZIP that ships its own verifier (a browser page and a
Python script), so a court, the DPA or the client can check it without this repository (ADR-0142).
Masking before a cloud model - names, companies, PESEL/NIP/REGON are replaced with tokens before
any cloud model (known gaps), and an egress guard checks every outbound call against the case's classification.