Pre-release · Open-core guarantee layer for Unreal Editor agents

A coding agent that operates a live Unreal Editor — and proves its work.

Kentledge is the verification contract that stands between an AI agent and your Unreal project. Every gate passes or refuses — signed, hash-chained, and checkable by strangers. Glue is commoditized. Guarantees are not.

Read the contract Get launch updates

$ kentledge proof ./MyProject PASS gate/compile artifact 9f31c2… fixture-set a1e0… signed ✓ PASS gate/anim-graph artifact 4bd7e0… fixture-set a1e0… signed ✓ REFUSE gate/engine-pin engine hash outside proven matrix → read-only mode ledger: 3 events appended · chain intact · verify with anyone's copy of the CLI

Why “kentledge”

Proof-load ballast

Kentledge is the dead weight stacked on a new structure to prove it holds — before anyone is allowed to trust it. Bridges, cranes, foundations: you don't argue the structure is sound, you load it and watch.

That is the product. AI agents can already drive an Unreal Editor: spawn actors, wire Blueprints, edit anim graphs. What no one gives you is the load test — deterministic evidence that what the agent claims it built is actually standing. kentledge proof is that test.

The moat is the contract, not the glue

Three schemas, published open

Whoever's schema becomes the way agents talk to engines — and read failures — owns the category. So the schemas ship open, permanently. Any fork that strips the refusal machinery visibly can false-green, and everyone can see that it can.

Open

`wire-protocol/v1`

How an agent addresses a live editor: transport-agnostic, capability-declared, identity carried in the schema itself — not bolted on.

Open

`error-envelope/v1`

No failure surface emits prose-only errors. Every failure is a coded envelope with a CI-tested resolution page behind it. “Something went wrong” is a build-breaking bug.

Open

`proof-envelope/v1`

The signed record of a gate outcome: artifact hash, gate id, assertion, fixture-set hash, verdict. The content is signed, not just the wrapper.

The buyer is an agent. The entity operating this product at failure time is usually the buyer's AI agent, not the buyer. Every surface — errors, docs, proofs — is machine-readable first, human-readable second. Start at /proof or /llms.txt.

Fail closed, always

Refusal is cheaper than support

Most agent tooling fails open: it proceeds, breaks something expensive, and pages a human. Kentledge is built on the opposite bet.

The refusal ledger. Every gate outcome — pass and refuse — appends a signed event to a local hash-chained log. The marquee claim isn't marketing; it's checkable by strangers with the verifier.
Engine-hash pinning. On an engine build the harness wasn't proven against, it drops to read-only observe, don't touch mode with a named status. Broken-API incidents become inert no-ops, never destructive surprises.
Resolution pages are code. A fix cannot publish unless CI reproduces the failure and proves the documented fix flips it green. No rotting docs an agent confidently executes on your project.
Regenerable beats generalized. Channels into your project are stamped per-project against a buyer-confirmed manifest — not a universal component that half-fits everyone.

Where this stands

Pre-release, gates first

▮ Kentledge is pre-release. The core layer — protocol, schemas, glue — will ship free and open on GitHub (kentledgehq). Paid tiers exist on paper only.

▮ True to its own rules, nothing here is for sale until the product passes its own gauntlet — including this page. No pricing, no payment links, until then.

▮ Want to know when it lands? One email, no list-selling, no tracking on this site.