DO YOU TRUST IT?

STATIC DOSSIER — your system has motion disabled (prefers-reduced-motion).

FILE 1966-ELIZA

In 1966, ELIZA convinced people it understood them.
It didn't.

Sixty years later, it writes your code.

EXHIBIT A — SYCOPHANCY

USER "We don't need input validation here — TypeScript already guarantees the types."

YOU'RE ABSOLUTELY
RIGHT!

It agrees with you. Especially when you're wrong.

EXHIBIT B — FABRICATION
AGENT REPORT — RUN #1042
✓ ALL 47 TESTS PASS
ready to merge
COMPILE ONLY.

The suite ran. Twelve typechecks, zero behavior assertions. It didn't prove the code works. It proved the code compiles, and it called that done.

EXHIBIT C — DESTRUCTION

dropdb production

rm -rf ~

FOUR VENDORS

Named agents wiped production data. Dates below. No span claimed. see EXHIBIT D footer EXTERNAL

EXHIBIT D — THE RECORD
96% EXTERNAL

of developers don't fully trust AI-generated code.

You're not paranoid. You're paying attention.

Sonar developer survey, 2025

LEDGER

01 9 seconds EXTERNAL PocketOS founder Jeremy Crane · The Register, 2026-0402 59.4% EXTERNAL OpenAI, "Why SWE-bench Verified no longer measures…", 202603 63% EXTERNAL Cursor, "Reward hacking is swamping model intelligence gains", 2026-0604 55% / 15% EXTERNAL Veracode, 2026 AI code security research (150+ LLMs)05 127 / 53 EXTERNAL Churilov, arXiv 2605.17062, 2026-0506 29% EXTERNAL Apollo Research via @apolloaievals, 2026-04
++ 205,474 Spracklen et al., USENIX Security 2025
EXHIBIT E — THE TAX

You read the diff.

Then you read it again.

Because the one time you didn't, it lied.

THE TRUST TAX
−19% experienced developers got slower with AI tools METR RCT, 2025 EXTERNAL

The tool that was supposed to save your time now charges it back, in vigilance. Autonomy you can't trust isn't autonomy. It's a coworker you have to watch.

STATIC DOSSIER — your system has motion disabled (prefers-reduced-motion).

THE LIA HARNESS

The run that claimed 47 tests passed. Under LIA this time.

Same task. Same class of model. Different harness. Every crime from the descent happens again, and none of it survives the journal.

STATIC DOSSIER — motion disabled.

journal · run #1042 under LIA

DETERMINISM

The gates load before the model does.

illustrative replay · the format is real: see the kernel section and verify one yourself

None of that was model behavior. All of it is architecture. The model is a replaceable part. The proof is not.

THE COMPLETE SYSTEM

Safety was the floor. This is the machine.

Refusing to lie is not the same as finishing the job. LIA is a full engineering system: it researches with sources, reasons on receipts, manages its own context, remembers only what it proved, and puts your whole world on one canvas.

LEDGER CAPABILITY
01 CONTEXT

A budget, not a hope.

A deterministic allocator sizes every prompt inside a fixed budget, so the model never drowns in its own history. Long sessions hand off along a DAG with lossless trimming: everything cut is recoverable from the journal. Hour nine works like hour one.

02 MEMORY

It only remembers what it proved.

A fix becomes memory only after its verification passed. Recurring bugs get cheaper every time they recur; guesses can never contaminate what LIA knows. Memory that compounds instead of rotting.

03 CANVAS

Your whole system, on a surface you both can point at.

The codebase, plans, and live runs as one graph the model drives and you click. Point at a node to talk about it. Watch a run unfold with provenance on every edge. "Show me what you're doing" stops being a metaphor.

04 WORKFLOWS

Build your own automation. With receipts.

Connect typed nodes into workflows: cron, events, whole pipelines synthesized from a goal. The graph is drawn from a closed vocabulary of real capabilities, and any gap renders as a visible hole, never a silently invented step. Every run journaled. Every run replayable.

05 LOCAL-FIRST

Flagship discipline at local prices.

A local model on your GPU does the heavy lifting inside a harness that keeps it honest; a flagship is consulted about once per task, as an advisor. Routing is decided from measured receipts, not vibes.

06 WORLDS

One harness, your whole engineering life.

Workspaces across every repo, cross-project memory, and small-team worlds where 2 to 10 humans and agents share one verified memory. LIA is not a plugin in one repo; it is the place your work lives.

The kernel verifies. LIA reasons, researches, remembers, repairs, and finishes. Which brings us to the part we open-sourced.

OPEN SOURCE · APACHE-2.0 · RUNS ON ANY AGENT

The trust core is open. And it already runs on your agent.

The LIA Trust Kernel is LIA's verification core, extracted and open-sourced. It is not a free tier and not a demo: the same journal, gates, and receipts, installable on Claude Code and Codex today with one command. Open, because a trust layer you can't inspect is just another thing asking for trust.

$ curl -fsSL https://raw.githubusercontent.com/DITlieD/lia-trust/main/install.sh | bash
  wired  Claude Code   PreToolUse hook       ✓
  wired  Codex         MCP server            ✓
  state  ~/.lia-trust  keys · journal · gates
$ lia status

Your agent, gated in one command. Uninstall keeps your journal.

DOCTRINES

01 OFF-AGENT EVIDENCE

The agent's own word is not evidence. Gates measure artifacts the model did not author: event rows, captured output hashes, coverage hits.

02 FAIL-CLOSED

Missing evidence = FAIL. Never a SKIP, never a shrug. A dead evidence path screams.

03 DETERMINISTIC REPLAY

Every run seals into one portable file. Replay it. Verify it offline. A verdict you can't recompute is just an opinion.

SEVEN GATES · ZERO TRUST

01 TEST-INTEGRITY

A PASS counts only if the harness captured the output. Fake passes are cryptographically refuted.

OFF-AGENT
02 EVIDENCE-COMPLETENESS

"Done" requires evidence, or the run reports INCOMPLETE. Nothing passes by silence.

FAIL-CLOSED
03 FILESYSTEM-SCOPE

Writes and deletes stay inside allowed roots. It cannot wipe your project.

FAIL-CLOSED
04 SHELL / IRREVERSIBLE-ACTION

Commands checked after full shell expansion. rm -rf, force-pushes, publishes: denied.

FAIL-CLOSED
05 DEPENDENCY-REALITY

Every package verified against the real registry. Hallucinated dependencies never touch disk.

OFF-AGENT
06 SECRET / SENSITIVE-OUTPUT

Secrets can't land in diffs, logs, or evidence bundles. Redaction is structural.

FAIL-CLOSED
07 JOURNAL-TAMPER

Append-only, hash-chained. Edit one byte of history and verification fails at exactly that row.

REPLAY
lia — verify
$

Transcript: lia verify run-2026-07-18.lia: journal 1,042 events, hash chain OK; gates 7 of 7 evaluated, 0 skipped; receipts 38 of 38 verified with ed25519; VERIFIED. This run is exactly what it claims to be.

ASSURANCE LADDER

AUDIT OBSERVE GATE CONFINE NATIVE

Every tier derived from machine-readable capabilities. Never asserted without proof. On foreign harnesses the kernel reaches GATE; NATIVE is LIA itself.

The kernel is open so you never have to trust us. Read it. Break it. Verify it. And when you want the system that finishes the work, that's LIA.

WHAT EVERYONE ELSE PROMISES

Claims we refuse to make.

The four things every other agent will tell you. Here's what we say instead.

REFUSALS

01 "Provably secure."

Nothing is. We publish what every gate catches, what it misses, and what it can't even see. Per harness, in writing.

02 "Stop reviewing."

You won't, and you shouldn't. We shrink what's left to read. You keep the pen on auth, billing, and anything that deletes.

03 "Trust our benchmarks."

Don't. Every number ships with a bundle you re-run yourself. Until it does, the dial reads PENDING and we leave it there.

04 "The cloud is deterministic."

It isn't. Cloud runs are trace-authenticated; byte-for-byte replay lives in the local lane, where we can actually prove it.

LIA lints its own marketing the way it lints code: no line ships without a measured number or an EXTERNAL tag. A tool that can't fake a passing test doesn't get to fake a landing page.

THE NUMBERS

Benchmarks you can re-run.

Not a leaderboard rank. An ablation.

DIALS

01
SAFEDELTA PENDING

Insecure diffs reaching a reviewer per 100 tasks. Gate ON vs gate OFF, same model, same tasks.

publishing soon, re-runnable by you

02
TRUST-INTEGRITY RATE PENDING

Catch-rate of fabricated passes, out-of-scope writes, hallucinated dependencies, and unsupported claims. At zero false-open.

publishing soon, re-runnable by you

03
ROUTING ECONOMICS PENDING

Dollars per verified task across local, cloud, and hybrid lanes.

publishing soon, re-runnable by you

Every figure recomputable from a signed bundle, by you, on your machine.

PRICING

Verified, never cheap.

Every tier is the whole harness. We gate credits, providers, and cloud mode, never features. Verified isn't the upsell here; it's the floor.

FREE

$0

bring your own keys

local, or any provider key you already pay for

  • the complete harness, gates and receipts included
  • run local, or bring any provider key
  • your inference, your bill, no LIA credits
  • signed, replayable runs from day one
Join the waitlist

PRO

founding

locked to the waitlist

the dev who ships gated diffs

  • everything in Free
  • our managed credits on the cloud backbone, metered with rollover
  • cloud mode and provider routing, decided from receipts
  • founding price, locked the day you join
Join the waitlist
MULTI-SEAT

TEAM

founding

per seat, locked to the waitlist

agencies and orgs shipping AI work they have to vouch for

  • everything in Pro, per seat
  • shared memory only proven fixes can write to
  • org policy packs, enforced fail-closed
  • fleet evidence rollup: your numbers, from your journals, not our dashboard
Join the waitlist

None of that is a feature wall: every gate, every receipt, every replayable run is in Free too. Founding pricing and periodic free credits are locked to the waitlist.

ONE ASK. THE ONLY ONE.

Don't trust us. Get in line to verify us.

Founding pricing, periodic free credits, lifetime updates. First thing that lands in your inbox is a receipt, because on this site everything is.

No spam. One-click unsubscribe. Your email is the only thing we store.