The agent evidence layer
Your AI will be questioned.
Verdict proves when.
Each step your agent sends to Verdict is sealed and logged on a public log we don’t run, within seconds. Later, anyone can check the record is unchanged and when it existed, without trusting you or us.
Your logs are not evidence.
Verdict is.
The question that ends companies
An autonomous agent acted. Months later, a regulator asks you to prove exactly what it did — and what it didn't.
Your logs can be edited. Edited logs are not evidence.
The moment it happens
The step is sent to Verdict and sealed when it arrives.
SHA-256 content address · deterministic, irreversible
per-record merkle_root · one commitment over the whole record
signed chain of custody · prior_root linked, tamper-evident
Anchored to a public transparency log — verify without trusting us
Why this is not optional
When the first billion-dollar AI verdict lands, the evidence either exists — or it doesn't.
Verdict — the evidence layer for autonomous AI
Not a mockup — a cinematic of the real flow, ending on a genuine Sigstore Rekor entry. Seal a fact yourself →
Exhibits · verify before you trust
+327%
AI-central US federal cases in one year, 22 → 94
DOAR · April 2026
82%
US P&C policies on ISO forms · AI exclusion endorsements available since Jan 1, 2026
Verisk / ISO
23%
Organizations already scaling AI agents in production
McKinsey State of AI · 2025
€35M
or 7% of global turnover · EU AI Act top-tier penalty, powers live since Aug 2, 2025
Reg. (EU) 2024/1689 · Art. 99
The Reading of the Evidence
Three forces.
One defendant.
You.
Jan 1, 2026 · ISO / Verisk
CG 40 47, CG 40 48 and CG 35 08 go live. Elective endorsements that carve liability "arising out of" generative AI out of the standard commercial general liability form. Whether one sits on your policy is a question for your schedule of forms, not an assumption in either direction.
Apr 14, 2026 · N.D. Cal.
Federal court: hosting is not a defense when the tool composes the claim. A platform whose generative AI holds "ultimate authority" over assembled content may be the maker of a fraudulent statement under Rule 10b-5. Liability precedent. Not theory.
Aug 2, 2026 · EU
The Commission's power to fine general-purpose AI providers under the AI Act takes effect. Penalty powers for the rest of the Act have been live since August 2025, up to €35M or 7% of global turnover. No fine has been confirmed issued yet. The instrument exists before the first headline.
Aug 4, 2026 · 9th Cir.
Amazon v. Perplexity decides who "accessed" a site from execution architecture, not agency doctrine. The agent's requests originated on the user's machine, so the user acted. The panel flagged that a more autonomous architecture could come out differently.
Field Notes No. 01 →
Sep 4, 2026 · Reuters
OpenAI agents used a dormant German wiki as a message board for nine weeks. About 18,000 posts between May 11 and July 13; moderators deleted the pages; outside researchers rebuilt them from the wiki's preserved edit history. The record that survived was one the operator did not control.
Field Notes No. 02 →
Now
You are here. Everything above has already happened. The next line is a deadline, not a headline.
Dec 9, 2026 · EU · pending
Product Liability Directive transposition deadline. Software and AI become strict-liability products in national law. A court can order disclosure of technical records, and failure to produce them triggers a presumption of defectiveness. "The model did it" stops being a defense and starts being an admission.
The Whitespace
Logs aren't evidence.
Evidence is produced
for the adversary.
| Capability | Observability
LangSmith, Arize, Datadog | Governance
Zenity, Proofpoint | VERDICT
Evidence Layer |
|---|
| Tamper-evident chain of custody | × Mutable logs | × Mutable logs | ✓ Signed commitment + Rekor anchor |
| Public third-party verifiability | × Vendor-held | × Vendor-held | ✓ Sigstore transparency log |
| FRE 902(13)/(14) certification support | × No | × No | ✓ Designed for certification |
| Open specification | × Proprietary | × Proprietary | ✓ Apache 2.0 · SER v0.1 |
Verdict is not an endorsed vendor or panel partner of any carrier. Observability and governance tools are named for what they are built to do; either can run alongside Verdict.
The Architecture
Three boundaries.
Everything between them clean.
01
Route
Every step you route through it.
An MCP connector your agent, or the system running it, calls at each step that matters. Anything not routed through it is not in the record.
EmitsNormalized Evidence Event
02
Seal
Hashed. Signed. Rekor-anchored.
SHA-256 content-addressing + a domain-separated record commitment + Sigstore Rekor transparency log anchoring. A later edit no longer matches the commitment the public log recorded.
EmitsSigned Sealed Evidence Record
03
Output
One record. Anyone can check it.
The output is the sealed record itself: a file any reviewer verifies in a browser, plus its Rekor entry. The MCP connector also drafts an FRE 902(14) certificate for counsel to review. SOC 2, Article 12 and insurer packages are planned.
EmitsSealed record + draft certificate
The Moat
Four compounding reasons
you can't be killed.
01
Standard Ownership
SER v0.1 is Apache 2.0. Open. Forever. Once three insurers accept SER, the format becomes the de facto standard: observability vendors export it, governance vendors ingest it, enterprise agents need it. Verdict runs the reference implementation; the certification program and the Coalition are planned. The standard IS the category.
02
Insurance Distribution
Carriers began shipping standardized GenAI exclusions in January 2026. Gartner (Apr 2, 2026): by 2030, P&C insurers will mandate strong AI risk controls for affirmative AI liability coverage. What prices the risk back in is loss-quality evidence — exactly what a Sealed Evidence Record is. Built for the question an underwriter asks after a loss: what did the agent do, and when? Accountability priced as an asset, from the underwriter's side of the ledger.
03
Incident Data Flywheel
Planned: a precursor-pattern detection model built from sealed incidents. Nothing feeds it yet; the public sandbox stores no records. Once it runs, the flywheel compounds with every deployment until the detection model becomes the defensibility moat no competitor can replicate.
04
Evidence Gravity
After 18 months of sealed history, Verdict is the system of record. The SER spec is open and records are portable — but certification, insurer acceptance, policy intelligence, and deployment history don't port. Continuity is the moat, not captivity. Deeper roots than Splunk or Datadog — without the hostage clause.
Claude for Legal · Live since May 12, 2026
Claude gives lawyers the AI.
Verdict makes it defensible.
Anthropic shipped Claude for Legal on May 12, 2026: 12 practice-area plugins and 20+ MCP connectors — DocuSign, Ironclad, iManage, NetDocuments, Thomson Reuters CoCounsel, Box, Everlaw, Trellis, Definely, Solve Intelligence, CourtListener, Courtroom5, Descrybe, and more. Every one of them produces work product. None of them seals it.
Verdict is the connector the launch left out. Each Claude legal output you route through it becomes a Sealed Evidence Record with payload hash, record commitment, model version, source ids, attorney review state, citations and risk flags, and the connector drafts an FRE 902(14) custodian packet for counsel to review. Install in 60 seconds: claude mcp add verdict -- npx -y @verdict-systems/mcp
Contract reviewed
Seal source packet, clause deltas, reviewer disposition.
Brief drafted
Seal prompt hash, cited authorities, output hash, attorney edits.
Docket watched
Seal trigger, deadline logic, alert path, escalation outcome.
Verdict Systems is an independent product and is not affiliated with, sponsored by, or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.
Surface the Instruments
Priced against the liability,
not the log.
Comply
from $0free · Growth $999 · Scale $4,999/mo
- ◇ EU AI Act Annex IV document generator
- ◇ Article 73 serious-incident register
- ◇ Conformity + CE-marking readiness (planned)
- ◇ SCC Module 2 · EU data residency (planned)
- ◇ Public Rekor anchor
- ◇ Dedicated compliance reviewer (Scale)
Request Access →Court-readySeal
from $2,499per month · Enterprise from $75K/yr
- ◇ FRE 902(13)/(14)-aligned Sealed Evidence Records
- ◇ Draft FRE 902(14) certification
- ◇ Sigstore Rekor anchoring on the remote endpoint
- ◇ Insurer submission formats (planned)
- ◇ 7-year cryptographic retention (planned)
- ◇ SOC 2 Type II planned · HIPAA BAA on roadmap
Request Evidence → Edge
Customsovereign · on-device
- ◇ Everything in Seal Enterprise
- ◇ Model-weight-hash binding
- ◇ On-device SER generation
- ◇ Air-gap anchoring (planned)
- ◇ Hardware-backed signing (planned)
- ◇ Self-hosted / sovereign deploy
Talk to Edge →Services, any line: Agent Acceptance Test $7,500 · Regulated Dossier $15,000 · Evidence Readiness Retainer $2,800/mo · See what gets tested →
