Verified Autonomous WorkChecked, attested, re-checkable

Autonomous work needs a verification layer. Verified checks every job an agent or robot finishes against the rules it had to follow, and attests the result so anyone can check it again.

Example data

Autonomous work
Verifiable by anyone

We are the lab building the verification layer for work done by agents and robots.

Define what done means

A Work Contract makes the conditions explicit. Every job is checked against the rules it had to follow.

Check against signed evidence

Facts come from the systems where the work happened. Missing evidence stays unknown, never guessed.

Make the result re-checkable

The claim, contract, evidence and decision travel together. Anyone holding the record can repeat the check.

Check a job
Change the evidence

The claim

INV-4711 is posted and matches purchase order PO-2208.

Expected amount: 12,400.00 EUR · tolerance: ±2%
Adjust the evidence4 inputs
All conditions hold
invoice-match / 1.0.0Local check
Claim / INV-4711

Invoice matched
to
PO-2208

DecisionSUPPORTED

Conditions4 / 4 TRUE

This is a local illustration, with no connection to live source systems. A supported decision needs every condition TRUE. One FALSE contradicts the claim; missing evidence stays UNKNOWN.

One protocol
Every part inspectable

From a claim to explicit conditions

Define what a finished job must satisfy. A Work Contract gives the check a precise, versioned set of rules, so “done” means the same thing to everyone.

Read the open specification ↗

The evidence stays close to the work

Source systems sign statements about what happened. Verified checks those statements against the contract. It establishes what was checked, not that a source system told the truth.

What a check can establish ↗

One file, checked without us

The claim, contract snapshot, signed evidence and decision are bound together by digests. A customer, auditor or counterparty can recheck the record offline, using keys they trust.

Explore the documentation ↗

Real work, explicit conditions

One protocol, different kinds of work. Explore the claim, the systems behind it, and where each process stands today.

Enterprise operationsIn production

Example claim

Invoice 4711 matched to its purchase order

Running with customers. Each completed match is checked against its Work Contract.

Illustrative industry context

Evidence from

ERP posting, purchase order and goods receipt

ResearchOpen protocol

Make the contract precise
Make the reasoning inspectable

Formal methods

64 theorems
Machine-checked in Lean 4

Verified’s contract semantics are formalized in Lean 4. The proofs establish properties of the formal model; they do not certify the truth of real-world source data.

Read about the formal model ↗

The Lab

A small research lab in Freiburg, Berlin and Zurich, working on one question: when a machine does the work, who can answer for it, and how?

Join the Lab

Research and engineering at one table, on the verification layer for autonomous work.

Bring us a process

We take on a small number of design partners, including for regulated processes. We write the Work Contract with you and run the protocol on live work.

Used only to contact you about access (privacy). Investors and everyone else: hello@beverified.ai