How it works Capture Catalog Provenance Enterprise

Trace shows you what your AI actually did. And lets you keep it.

Every time you ask an AI for something, a lot happens behind the scenes that you never see. Searches run. Scripts execute. Files get read. Trace records all of it, seals it so nobody can alter it later, and lets you save the parts that worked so you never have to figure them out twice.

Trace - Session 7F3A - Request 12 root: computing…
WHAT HAPPENED - CLICK A STEP FOR DETAILS, PIN TO SAVE
Catalog
Your saved steps. Verified. Reusable in any session.
Nothing saved yet. Click "Pin" on any step to keep it forever at a udm:// address.
SHA-256 hash chain. Tampering breaks the seal.
$ trace verify udm://segment/a91f…3c2e  hash matches address  
Determinacy encoding

Know what worked before you read a word.

Each step gets a colored bar on the left edge. Green means it ran and the result checks out. Amber means it ran but nobody verified it. Red means it broke. You can scan a whole session in seconds.

Verified

It ran, and the result is confirmed. You can rely on it.

Provisional

It ran, but the result hasn't been checked yet.

Blocked / Failed

It failed, got blocked, or didn't have what it needed to run.

Executing

It's still running. Watch it finish in real time.

Capture

Three ways to capture. One format for everything.

Whether you use a hook, a proxy, or a browser extension, everything Trace captures ends up in the same format. That means records from different tools can be compared and checked against each other.

Hook Capture

Hooks fire after a tool finishes and record exactly what went in and what came out. The model never touches this data. It is the most trustworthy source, observed:hook.

Proxy Capture

A small proxy sits between your app and the AI provider and records the traffic. You change one setting and you are done, observed:proxy.

Extension Capture

A browser extension watches the conversation as it appears on screen. The easiest way to start, observed:extension.

Reconciliation Engine

If you run more than one channel at once, Trace compares what each one saw. When they disagree, it tells you plainly instead of quietly picking one.

The Catalog

Save the steps that worked. Use them again.

Pin any step and it is yours forever, stored at an address based on its own fingerprint. Bring it into a new session months later and you get back exactly what happened the first time. Not a summary. The real thing, verified.

udm://segment/<hash>
Everything you save gets a permanent address
SHA-256
Every record is sealed against tampering
<$200/mo
Runs on standard cloud at pilot scale
Provenance taxonomy

Trust comes from how something was captured, not what it says about itself.

If the AI says "I searched the web," that is a claim, not proof. Trace only calls something observed when a hook, proxy, or extension actually saw it happen. A claim can never be promoted to proof.

TagSourceTrust model
observed:hookPostToolUse hookThe real thing. Nothing ranks above it.
observed:proxyAPI stream interceptionVery accurate, with full context.
observed:extensionBrowser DOM / networkScreen-level detail. Good, not perfect.
reported:modelModel's self-assertionA claim, not proof. Stays that way.
derived:transcriptPost-hoc transcript parsingReconstructed after the fact. Fills gaps.
Enterprise

Built to hold up under scrutiny.

Put the proxy in front of your company's AI traffic and every interaction is recorded with a tamper-proof trail. When an auditor or regulator asks what happened, you don't reconstruct it from memory. You show them the record, and the math backs you up.

Stop losing what your AI actually did.

Done!