Your AI says it’s done.
Prove it.

Ground the work. Check what holds. Close with a receipt, not a vibe.

GAVEL checks a named artifact against your declared requirements and returns a verdict bound to a receipt — one you can recompute yourself. See what passed, what failed, and what remains unverified, before the handoff.

Run a real check Read the contract →

Free launch demo · no API key · every account starts with $3 of credit monthly.

Abstract illustration: a precise document outline with a single amber verification seal, over a faint measurement grid. — Illustration — generated artwork, not a product screenshot.

How to read a result

Yes

Every claim in scope was assessed and held.

At least one assessed claim failed. Read the rows — NO does not mean every row was assessed.

Abstain

One or more claims could not be assessed. A completed answer, not a failure — and never a pass.

Provisional

Not produced by the numeric checker. Other surfaces carry their own words.

What a receipt looks like

# POST /api/verify { "claim": "6 * 8 = 48", "band": "math" } # response { "register": "YES", "recompute": "left = 48; right = 48; equal = True", "reason": "exact_numeric_comparison", "receipt": "safe-arithmetic:c3468ad95735899265dbcef44d069b9a2a23cf8feed32665a19f960bed10f21d", "receipt_recipe": { "algorithm": "sha256", "fields": ["version","input","claims","summary"], "note": "Repeatability and input/result binding, not a signature or execution permission." } } # recompute it yourself — verified independently, 2026-11-09 # sha256(canonical JSON of {version,input,claims,summary}) # reproduces the published receipt exactly.

First-visit glossary

GAVEL™: The verification engine. It checks a named artifact against declared requirements and returns a verdict.
Receipt: A hash-bound record of exactly what was checked and what the check returned. You can recompute it yourself.
Bounded: It checks only what it declares it can check — and says so plainly when something falls outside that scope.
Register: The verdict word: YES, NO, ABSTAIN, or PROVISIONAL.

What GAVEL does not certify. It does not certify complete security, certified truth, a proof of model reasoning, or external replication. A receipt proves its stated binding — not a broader guarantee. Unverified is never a pass.

Why this is here. The “claim ceiling” is the most persuasive block on the current site precisely because it lists what the product does not do. It earns more trust than a promise would. Keep it.

Current — as published

Trust backbone for AI / SI

Build what people
come back for.

Build reliable, repeatable work that stays economically valuable and sustainable to run. Ground the work. Check what holds. Close with a receipt, not a vibe.

Get started free Try the demo →

Why this underperforms

Problem 1 — the headline says nothing

“Build what people come back for” could headline a CRM, a design agency, or a loyalty app. A stranger reads it and still does not know what GenXis sells.

Problem 2 — four terms before one definition

GAVEL, receipt, bounded and register all appear before any of them is explained. The vocabulary is a differentiator for insiders and a wall for newcomers.

Problem 3 — the best line is buried

“Your AI says it’s done. Prove it.” already exists on get-started-free. It is the strongest line on the site and it is on a secondary page.