Software has compilers that make programs executable, type systems that establish their properties, and proof systems that let a computation be checked independently. For work, the analogue is missing. An agent claims it reconciled an account — what does that claim mean, which evidence is sufficient, and how can anyone verify the result without seeing confidential data? We are writing the compiler of work done.

The problem, technically

A Work Contract is a program that specifies what successful execution means. We are building the pipeline that compiles it:

Work Contract → formal semantics → verification IR → evaluator / proof circuit → verifiable Work Record.

The open problems run the whole length of that pipeline. How is work completion expressed as a precise, composable, machine-evaluable contract? How does Lean 4 fix the semantics of contracts, claims and evidence — and how is that semantics preserved through compilation? How is evaluation made deterministic and reproducible in Rust, with small auditable components and explicit trust boundaries? And where evidence cannot leave its owner: how does evaluation compile to a zero-knowledge proof that establishes exactly what the contract states — no more, no less? The first leg of that pipeline exists in public — the contract semantics and a growing set of theorems are Lean 4 in the open protocol repository — the last leg is research. We don’t claim cryptography can establish arbitrary real-world truth; the model accounts for evidence provenance, source trust and the limits of each proof.

Who we’re looking for

You think like a programming-languages researcher, reason like a formal-methods engineer, and build like a systems programmer. In practice: Lean 4 or another proof assistant; semantics, type systems and intermediate representations; Rust; and ideally SNARKs, STARKs or zkVMs. A PhD in programming languages, formal methods or cryptography is welcome, not required. This is a founding role with a genuine research mandate — we publish where the work deserves it.

Done means — first six months

  • Work Contracts have a formal semantics, machine-checked in Lean 4.
  • A first verification compiler runs in Rust: contract to IR to deterministic, reproducible evaluation.
  • For selected contracts, evaluation compiles to a proof that establishes exactly what the contract states.

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