Beavan | Building the AI Liability Layer (@BeavanAI) header
Beavan | Building the AI Liability Layer (@BeavanAI) profile picture

Building the AI liability layer! Cryptographic proof of what an AI did & under whose authority. 3 patents filed. https://teapawt.net/t.co/xLzeHCRrzv. Building in public

Houston TX
Joined September 2021
Replying to @kittyrunfast
keep going your doing great Cat!
8
Nice to meet you Hanna. Happy to connect.
2
3
46
Replying to @empowwerr
Great to meet you as well John. Love to hear about what you are working on.
3
Beavan | Building the AI Liability Layer retweeted
Wells Fargo's online banking agreement changes on Nov 24. It adds a section on AI agents, and seven words in it matter: "You must retain evidence of such revocation." You turn your agent off. A transfer still goes out. What do you hand the bank? 38 seconds:
3
1
11
219
Each Verdict record gets a timestamp from Sigstore’s public log, which we don’t run. Anyone can check it without us. If your agents will answer to an auditor or an insurer, DM me.
8
50
The company that runs your AI agent usually holds the key that signs its logs. If last month’s logs ever got inconvenient, they could rebuild them and sign them again. Their own checks would pass. That’s the problem I’m building Verdict for.
Every AI agent that moves money, reads patient records or signs contracts is going to get questioned. A log the operator can edit won't answer that. Verdict seals what the agent did and anchors it to a public log we don't run. Anyone can verify it without us.
4
13
216
AI governance comes down to four layers: regulation, standards, roles, controls. Every one ends with the same request: show me the record. So we drew where the record sits, and 12 industries that will be asked for it. What a seal proves, and what it doesn't, is on the chart.
2
4
12
389
Replying to @alex404
Looked at Fleurir. That's where it fits: when Fleur's agents book the pottery class or the SF weekend, the record holds what the user asked and what each agent sent back, sealed as it happens. Which flow would you test first, the class booking or the trip?
21
Replying to @AthenaPrime
Canonicalization. Our Python verifier leaned on json.dumps, which sorts keys and writes floats differently from the spec, so some genuine records failed. I rewrote it to the spec's own rules, and that fix went public today.
1
94
Replying to @alex404
Yes, if it's passed in. The record has separate hashes for the request and the tool's response, sealed together in one record. It can't capture the response on its own: whatever runs the tool hands it over. The CAGE adapter seals the hash the gateway sends.
1
1
14
I built Verdict, so a stranger can check our work without calling me. The image is a real run. 24 test vectors pass, and the record checks against a public log we don’t run. What do you need to see before you trust her record you didn’t make?
Every AI agent that moves money, reads patient records or signs contracts is going to get questioned. A log the operator can edit won't answer that. Verdict seals what the agent did and anchors it to a public log we don't run. Anyone can verify it without us.
1
3
87
A Google open-source agent governance repo merged a Verdict adapter six days after I opened the PR. Then its maintainer wrote 4 live tests that hit our API over the wire. AI agents are starting to move money, read patient records and sign contracts. When something goes wrong, someone will ask what the agent did. A log the operator can edit won't settle that. Verdict seals what the agent did and anchors it to Sigstore Rekor, a public log we don't run. Anyone can check a record without asking us. The spec, 24 test vectors and verifier are open under Apache 2.0. Right now I'm closing our first paid design partner. We meet every week with an insurance partner. A sovereign AI company in the Gulf has asked to build with us. And we filed comments on the NAIC's draft for evaluating AI risk at insurers. If your agents will answer to an auditor or insurer, DM me.
9
3
1
12
672
Replying to @SKILLGENESISAI
Anytime! What are you building?
1
13
I’ve realized something about being a founder: You have to be willing to see something that doesn’t exist yet, and believe in it long enough to make other people see it too. That’s the part I love. Starting with an idea. Turning it into a product. Turning the product into a company. And eventually building something that can change an industry. I’m not interested in building small. I want to work with ambitious people, tackle difficult problems, and build technology that matters. Still early. Still learning. Still building. But the vision keeps getting bigger. If you’re a founder, engineer, investor, or just obsessed with building the future, let’s connect.
6
14
140