Themiz

Themiz takes the mechanics of a court case off your desk: it reads the file, hunts case law, and reviews its own documents.

Русский · 中文

Hello. I am a practising lawyer, and too much of my time went into mechanics: two hundred pages of scans, dates to reconcile, citations to check, one detail buried somewhere in the file.

Themiz takes that work and leaves me the part that needs judgement. She does not decide anything, and neither should she.

— Filipp Zarubin

Contents

• What This Is
• Why It Helps
• The Main Advantage
• How It Works
• Quickstart
• Simple Comparison
• Simple Words
• Safety And Privacy
• Limits
• Star And Contribute

What This Is

The project was renamed: Themis is now Themiz, spelled like the rest of the Olympuz family. Old GitHub links still redirect here, but an existing clone or fork needs git remote set-url to follow.

Themiz works next to a lawyer. It reads the file on your computer, builds a case map, hunts practice for you and against you, drafts a document and hands it to a different agent for review. The decisions stay with you, and that is the design, not a disclaimer at the end.

Why It Helps

A good lawyer's time does not go into law. Two hundred pages of scans. Reconciling dates. Checking citations. That one detail that was definitely somewhere in volume three. Themiz takes that part whole and leaves you the part where thinking happens.

The Main Advantage

Main advantage: the numbers and the text of the law come from a program, not from a model.

Why this is better: Statutory interest, procedural deadlines, court fees and amounts in words are computed in code. Statutes are quoted from the corpus on your own disk, so a paraphrase cannot quietly replace the article.

How It Works

A case moves through stages. Each has its own agents, and no document leaves without a second pair of eyes.

  ┌──────────┐   ┌──────────┐   ┌──────────┐
  │ Intake   │ ▶ │ Extract  │ ▶ │ Case map │
  └──────────┘   └──────────┘   └──────────┘
        ▼
  ┌──────────┐   ┌──────────┐   ┌──────────┐
  │ Research │ ▶ │ Council  │ ▶ │ Draft    │
  └──────────┘   └──────────┘   └──────────┘
        ▼
  ┌──────────┐
  │ Hearing  │
  └──────────┘

Step 1: Hand over the case files

You drop the file into the case folder. Client folders are closed from publication at the repository level, so material stays local.

You get: one folder per case, with everything the work will need.

Step 2: Scans are read on your Mac

Recognition runs locally, about a second and a half per page. Registration numbers, case numbers, and amounts are pulled out and checked by their control digit without going online.

You get: readable text with the key details already verified.

Step 3: The case map is built

Facts move from the documents into a single map: who, when, what is claimed, and what proves it. A separate agent cross-checks the readers against each other.

You get: one place to look instead of rereading the whole file.

Step 4: Case law for and against

One agent looks for practice that supports your position, another for procedural moves, and a third deliberately hunts practice against you. The search request is depersonalised.

You get: both sides of the argument before the other side makes it.

Step 5: Five jurists argue it out

Five reviewer agents take the position apart from different angles and put it back together. Disagreement is the point: a weak argument is meant to fall here, not in court.

You get: a position with its weak points already named.

Step 6: One writes, another checks

The document is written by one agent and reviewed by another that did not write it. Assembly before review is refused, the format is checked before filing, and a guard runs over personal data on every commit.

You get: a draft you edit as a lawyer, not a text you have to re-verify line by line.

Step 7: Hearing prep and reminders

Deadlines are calculated with the working calendar and a reference to the rule. A local dashboard shows the state of the work. Reminders go to your own bot, carrying dates only.

You get: the hearing prepared, and edits you make teach the next document.

Quickstart

You need a Mac for scan recognition, Python 3.11 or newer, Xcode Command Line Tools, and Claude Code.

git clone https://github.com/zarubinvibe/themiz.git
cd themiz
claude
# inside Claude Code run: /themiz-setup

Prefer the plain installer? Run bash install.sh in the same folder; it installs dependencies after one confirmation but skips the interview about your practice. No Git? Take the ZIP. The local dashboard starts with python3 cockpit/app.py on port 8800. First time here? Open the project in Claude Code and run /themiz-setup: the install goes as a conversation, one question at a time, and nothing is installed without your yes.

Never done this before? The onboarding walks the whole first run step by step and says what you see after every command.

You get: the setup asks about your practice one question at a time, downloads the codes you need first, and ends by testing itself on a real document of yours.

Simple Comparison

Simple Words

Safety And Privacy

• Reading and recognition run on your computer; client folders are closed from publication at the repository level.
• Case law search sends a depersonalised request, never the case file.
• A cloud check of a single page is allowed only when local recognition returns nothing or a critical detail must be confirmed. There is no silent switch to the cloud.
• Telegram reminders use your own bot and carry dates and the word "done": no names, case numbers, or amounts.
• A personal-data guard runs on every commit, and a separate guard refuses to erase case material.
• Document format is checked before filing, and assembly before review is refused.

Before putting client material on a shared computer, read SECURITY.md.

Limits

Status: in development, built to work under a lawyer's control. The main path runs through Claude Code.

• Local scan recognition depends on Apple Vision and works on macOS only. Text PDF, DOCX, and XLSX are read on other systems too.
• Case law search depends on an external source and is sometimes unavailable.
• A red gate or a missing agent stops the workflow instead of guessing.
• Themiz does not represent you, does not sign anything, and does not replace a lawyer's judgement.
• A clean install on Windows and Linux has not been verified yet.

Deeper: how it really works, in Russian and without advertising, and the full reference with the agent roster.

Star And Contribute

Useful? Give Themiz a star: https://github.com/zarubinvibe/themiz. It takes a second and it decides whether other people ever find the project.

Want to change something? The path is short: fork the repository, create a branch, commit your change, push the branch, then open a Pull Request. Do not push directly to main; the release gate rejects it.

Found a problem instead? Open an issue at https://github.com/zarubinvibe/themiz/issues and say what you ran and what happened.

Olympuz family

This is one of the public Olympuz projects. Each row opens the repository or downloads its source as a ZIP.

License

Themiz Community Licence 1.0: free for an individual lawyer, including private practice. Organisations need a commercial licence. See LICENSE and LICENSE.ru.md.