Technical deep-dives on AI verification, security audits, and trust infrastructure.
Public Agent Decision Safety Benchmark: 21 curated stop-cases across payments, travel, and enterprise. Ungated baseline false-allow rate 1.00. Live ThoughtProof DQL gate: 0.00 — judgment-backed, five axes, objections on the wire. Real receipts, not mockups.
An agent can have identity, a reputation score, a funded wallet, and a signed payment — and still pay the wrong invoice. The transaction is perfect; the decision is catastrophic. Identity, registries, and credit scores enable action. They do not create judgment. Why the missing layer is verification before irreversible execution — with public evidence from our live counterfactual experiment.
Everyone agrees you want a check before an autonomous agent acts. Almost nobody measures what it's worth. So we ran the counterfactual live, with real capital: two identical agents, same model, same market — one clears ThoughtProof before every action, one doesn't. After 28 days the verified agent held $796 while the unverified one dropped to $25. Not from predicting the market — from blocking 733 trades whose reasoning didn't hold.
Identity, authorization, and security each answer a question about an agent's action. None of them answers the fourth: is the plan actually a good idea? That's the decision quality layer — an independent, model-agnostic check that judges whether an agent's reasoning holds before it acts. Plus what's launching: a browser extension and an MCP proxy.
Dev-time testing asks "did you build it right?" Runtime verification asks "is this decision, right now, well-reasoned?" Two different layers of the same stack — like Datadog vs. Jest. With real data from a live trading agent: 21.4% vs. 72.3% drawdown, and zero blocks on well-reasoned trades.
ALLOW/BLOCK is a dead end. The useful signal is the objection — the specific reason a decision failed. Structured objections turn a gate into a self-correction loop, where the agent reads the critique and fixes itself before execution. With a live agent that caught its own hallucinated premise and stood down.
A real-world case study from a live ERC-8183 co-evaluator exercise. Two independent evaluators, two on-chain settlements, and a verification pipeline that caught its own mistakes before they became permanent.
150 sentinel cases, 10 models, 1500 evaluations. Rasch psychometric calibration reveals which AI judges to trust — and which broke under production load. SERV models outperform frontier models; Gemini and nano flagged as misfits.
SERV Reasoning vs. our prior production cascade across 120 plan-level verification cases. 107× performance per dollar, 0 false ALLOWs, 0 API failures. Why the reliability number matters more than the cost headline for banking and MRM — and why this changes what PLV can be deployed as.
Three chatbots. 15 questions a bank risk officer would ask. Every answer verified against the actual regulation. Correct risk identification ≠ regulatorily compliant answer.
A pattern keeps showing up in the agent-verification literature: a single verification stage is not enough. You can verify what an agent plans to do before it acts. You can verify what an agent actually produced after it acts. These are different problems.
AI prior authorization has workflow, decision, and governance layers. What it still lacks is a verification layer. The next bottleneck is no longer throughput. It is defensibility.
Good agent plans often look incomplete when verifiers assume the same granularity as the reference trace. ThoughtProof v2 shows why segment-aware support is the structural fix.
A new Oxford/NYU paper on ERC-8004 trust architectures identifies the gap between cryptographic integrity and decision alignment. Proofs guarantee integrity, not alignment. Here's the missing layer.
We found a theoretical attack vector in our own multi-model verification pipeline. Then we shipped the fix — in the same session. Three layers of injection defense, inspired by Anthropic's Sectioning pattern.
Ethereum's Trustless Agents standard defines identity, reputation, and validation registries for AI agents. The Validation Registry is still a design space. Here's how epistemic verification fills it.
Harvard, MIT, and Stanford red-teamed AI agents for two weeks. They found 11 failure categories. We found the same patterns in our own audits — and we're building the fix.
Article-by-article mapping: how multi-model verification satisfies Art. 9, 13, 14, and 43 — with code examples and an honest assessment of limitations.
Discovery → Orchestration → Verification → Trust. Most teams stop at Layer 0. The real risk lives in Layer 2.
How we turned 20+ real security findings into automated detection rules — and what the false positive journey teaches about AI security tooling.
How to systematically audit Model Context Protocol servers for prompt injection, authority bypass, and trust boundary violations.
Claim → Perspectives → Synthesis → Hash. Everything else builds on this: receipts, trust scores, cross-agent verification.
When models disagree, most systems pick the majority. We preserve the dissent — because the minority opinion is often right.
Perplexity, LangChain, and CrewAI solve orchestration (Layer 1). ThoughtProof solves verification (Layer 2). Here's why the distinction matters.
We asked Grok to verify its own output, then ran the same claim through the full pipeline. The results are instructive.
Spoiler: No. But the failure mode is fascinating and reveals exactly why multi-model verification exists.
When AI agents call other agents, how do you verify the chain? Epistemic blocks create a verifiable provenance trail.
Parallel execution, smart routing, and when to skip verification entirely. Latency numbers from production.
The first npm package for epistemic verification. What's in it, how to use it, and what's coming next.