K Kar · karma-didy
FallForge estate · sovereign build
Provable AI, not persuaded AI

Proof by re-running it — never an opinion from a model.

This is a small family of narrow, deterministic verifiers for AI-adjacent claims. Each one answers one specific question and gives you an artifact — a receipt, a diff, a proof — that anyone can recompute independently and get the exact same byte-for-byte answer.

No model is asked "does this look right?" None of these tools judge, grade, or vibe-check. They check a specific, falsifiable thing against a specific, disclosed source, and they show their work.

11
verifiers, live
0
LLM judges used
1
question each answers
100%
re-runnable by a third party

What this is / isn't

Is: a curated set of narrow verifiers. Each one checks a specific, well-defined claim against a source you provide, and produces a deterministic result plus a reproducible receipt or hash.

Isn't: a fact-checker, a truth oracle, or a general AI auditor. None of these tools evaluate whether a claim is true in the world — only whether it holds up against the specific evidence you gave it. They don't grade quality, safety, or intent. Scope stays deliberately small so the answer stays provable.

The verifiers

11 tools, each opens its own live page
01 / 11

CiteLock

VERIFIED NEAR MATCH NOT FOUND

Verify a claimed quote is genuinely present, verbatim, in a source you paste. Tells a clean quote apart from an altered paraphrase or a fabrication outright, with a reproducible receipt.

kar-citelock Open
02 / 11

Kar-Veil

FAITHFUL STRUCTURE BROKEN

Prove a redacted document is structurally faithful to a committed original. Catches an edited, forged, dropped, or reordered line — without ever seeing the hidden content.

kar-veil Open
03 / 11

FairDraw

MATCH DIVERGED LEAKAGE FOUND

Recompute a claimed "random" eval sample or train/test split from a disclosed population, seed, and size, then diff it byte-for-byte — catching train/test leakage a claim alone would hide.

kar-fairdraw Open
04 / 11

Conform

PASS FAIL SHA-256

Deterministic JSON Schema conformance for AI structured output. PASS/FAIL with exact violation paths, plus a canonical hash that tells reformatting apart from real content drift.

kar-conform Open
05 / 11

Kar-Warden

INTACT DRIFTED BREACHED

Check an AI component's observed state against a declared warrant — config, capabilities, files, invariants. One severe break is enough to block; nothing needs a human to spot it.

kar-warden Open
06 / 11

Kar-Anchor

MERKLE ROOT INCLUSION PROOF

Commit a batch of content to one Merkle root you can publish anywhere, then hand out per-item inclusion proofs that anyone can re-check offline, with no shared ledger required.

kar-anchor Open
07 / 11

Wisp

CONFIRMED CONTRADICTED

Check an AI's claims about a public GitHub repo — files exist, a gate passed, phrases are present — against GitHub's own public API. Catches an agent claiming work it never did.

kar-wisp Open
08 / 11

Glyphguard

CLEAN HOMOGLYPH SMUGGLING

Scan text — a prompt, an output, a pasted doc — for the tricks that hide in characters: invisible/zero-width chars, homoglyph lookalikes, bidi overrides, and hidden Unicode-tag payloads (ASCII smuggling). Deterministic, byte-for-byte re-runnable report.

kar-glyphguard Open
09 / 11

Kar-Shingle

IDENTICAL NEAR-DUPLICATE DISTINCT

Find near-duplicate documents that exact-hash dedup misses — padded or lightly reworded copies. Word-shingling + MinHash gives a re-derivable IDENTICAL / NEAR-DUPLICATE / OVERLAPPING / DISTINCT verdict plus a recomputable receipt.

kar-shingle Open
10 / 11

Kar-Canon

MATCH DIFFERS SHA-256

Prove two differently-formatted JSON documents are byte-identical after canonicalization (RFC 8785-aligned: sorted keys, normalized numbers, minimal escaping) — or pinpoint the exact path where they diverge. Reproducible in any language.

kar-canon Open
11 / 11

Kar-Tally

WITHIN CAP OVER CAP GAP

Recompute an AI agent's spend log — cap minus cumulative cost — to prove the balances are consistent, gap-free, and the budget cap was never exceeded, even if a later balance was edited to hide an overspend.

kar-tally Open

The shape of every tool

same pattern, eleven times
STEP 1

You give it evidence

A source document, a population, a schema, a warrant, a repo — something disclosed and fixed, not a vibe.

STEP 2

It runs a fixed check

A deterministic function, not a model call. Same inputs always produce the same output, every time.

STEP 3

You get a verdict + receipt

A plain result plus the artifact behind it — a hash, a diff, a proof path — so the claim is checkable, not just stated.

STEP 4

Anyone re-runs it

A third party with the same inputs gets the same byte-for-byte answer. That's the whole proof — no trust required.