About ZTL Judge
ZTL Judge is a local studio for evaluating claims and self-referential systems with a deterministic ZTL core. An optional LLM translates natural-language claims into ZFL tables, while the core—not the LLM—produces the verdict and an auditable back-reading.
Key features
- 01Translate claims into ZFL tables with optional AI
- 02Validate and edit tables by hand
- 03Deterministic verdicts with warranty grades
- 04Quarantine passports for self-referential systems
- 05Back-reading without AI
- 0641 worked examples
Use cases
- 01Evaluate a claim expressed in natural language
- 02Inspect how unverified inputs affect a verdict
- 03Analyze paradoxes and self-referential systems
- 04Review the core's reading of a ZFL table
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.vitalyreznik.com/mcpclaude mcp add --transport http inventor1975-ztl-judge https://api.vitalyreznik.com/mcp{"mcpServers":{"inventor1975-ztl-judge":{"type":"http","url":"https://api.vitalyreznik.com/mcp"}}}Open in Cursor{"servers":{"inventor1975-ztl-judge":{"type":"http","url":"https://api.vitalyreznik.com/mcp"}}}Open in VS Code{"mcpServers":{"inventor1975-ztl-judge":{"type":"http","url":"https://api.vitalyreznik.com/mcp"}}}{"mcpServers":{"inventor1975-ztl-judge":{"serverUrl":"https://api.vitalyreznik.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
3This tool takes no parameters.
Details
From the project READMEZTLStudio
The AI translates; the measured core judges — truth is never granted on credit, not even to the translator.
A local studio for judging claims and paradoxes. You state one in natural language (any language); an LLM only translates it into ZFL, the formal table language — it never judges. A deterministic, measured ZTL core does the judging: verdicts with warranties, quarantine passports for self-referential systems, and a deterministic back-reading that verbalizes exactly what the core read from your table.
The pipeline embodies the logic it serves: the LLM's output is an unverified
input (the mark Z), and the core is the customs house — truth is never
granted on credit, not even to the translator.
human ──meta-chat──► the AI fills a ZFL table (rows + a claim), you sign off
│
▼ validator ──► the deterministic core judges
▼ back-reading (no AI — the second auditor)
▼
verdict · warranty · passport · stipulations
Run
python3 ztlstudio.py # → http://localhost:8190
Python stdlib only; the ZTL core is vendored in ztlcore/, so a clone is
self-contained (no submodules, no dependencies). The AI is optional: with no
key the studio runs in pro mode — fill the ZFL table by hand. To enable AI
translation, open ⚙ Model, pick a provider + model + key, or set the env
var, or drop a key into a local .<provider>_key file (all gitignored — no
keys ship).
What you hand it: one table, no genre to declare
ZFL v2 is a single table of rows plus a claim. Each row states a fact,
its status (T verified / F refuted / Z unverified — the zero-trust
default), its ground, and — importantly — what it means in words (the
polarity auditor: it lets the back-reading catch an encoding that says the
opposite of what you intended). You never declare whether this is a "statement"
or a "paradox": the genre is computed, and whichever instruments apply fire
— a verdict + warranty for a claim, a passport for a self-referential system.
The studio ships 41 worked examples — open one to see the exact shape of the table, then edit it. The back-reading verbalizes what the core actually read, so your translation is audited by a component that cannot hallucinate.
The workflow
- Meta-chat — describe the claim in your language; the AI fills the table's rows and asks only when formalization is genuinely blocked. It knows its boundary: arithmetic, quantities and numeric wordplay get an honest "does not formalize into propositional ZTL", never an invented encoding.
- The table — a grid of rows, the grounds bar, and the claim line, all hand-editable (pros skip the chat entirely). Run validates and judges; validator issues are machine-readable and can be fed back to the AI to repair.
- The report — the core's verdict, its warranty grade (hereditary / sound / until-verification), the passport of unverified inputs, and the completion table — followed by the deterministic back-reading and an optional AI explanation that retells the verdict and is forbidden to re-judge (labeled unverified by definition: the pipeline applies its own logic to itself).
What the core reports
- Claims — the verdict (
T/F— verdicts are always two-valued;Zis a mark on an input, never a verdict), the warranty grade, the passport of unverified inputs, and the completion table showing how the verdict behaves under every reading of the unverified rows. - Self-referential systems — the grounded part (identical in every fixed point), the quarantine set, and a passport per component: PARADOX (no classical solution — permanent refusal, with the oscillation period), UNDERDETERMINED (refusal until stipulation), INPUT (until verification), DOWNSTREAM (inherited).
Providers
Keys stay on this machine, read in order: the Settings field, the env var
(GROQ_API_KEY, ANTHROPIC_API_KEY, …), then a local .<provider>_key file.
Supported: Groq, Anthropic (Claude), OpenAI, OpenRouter, DeepSeek, Gemini,
xAI, NVIDIA. A stronger model formalizes cleaner; the core judges the same
regardless of who translated.
Related
- ZTL — the logic itself: the kernel, the papers, and the ZFL language.
- introspect — the same zero-trust core applied to code: a taint analyzer for seven languages.
AI disclosure
Built by Claude (Anthropic) as architect and implementer, with Vitaly Reznik as human curator and decision-maker, under a strict honesty discipline: mark boundaries honestly, measure — don't guess, and never claim more than was verified.
License
Dual-licensed under MIT and Apache-2.0 (see LICENSE-MIT,
LICENSE-APACHE).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.