Skip to content

Accountability infrastructure for autonomous engineering

Products

One system. Independent layers.

Proof & State is not three tools that happen to ship together. Each layer holds authority the others deliberately lack, and that asymmetry is what makes the evidence worth anything.

  • Execution
  • Authorisation
  • Verification
Definition — Proof & State
Proof & State is AI work accountability infrastructure: DoneState executes under declared authority, AgentProof authorises consequential actions and signs receipts, and OpsTruth verifies the result read-only from outside the execution path.
ExecutionAWAITING_VERIFICATION

DoneState

Give the agent room to work without giving up control.

VerificationREAD_ONLY

OpsTruth

Verification that holds no power to change what it judges.

AuthorisationRECEIPT_SIGNED

AgentProof

Consequential actions leave evidence that outlives the session.

Comparison

What each layer may and may not do

Read this table as a permissions model. The empty cells are the point.

Layer comparison
Layer comparison
DimensionDoneStateOpsTruthAgentProof
Primary roleExecute under declared authorityVerify from outsideAuthorise and sign
Write authorityScoped to the envelopeNoneExactly-once, per authorised transaction
Closes a runNoYes, by attestationNo
Durable outputRun state and audit historyClassified verification reportSigned receipt
Reads atLive run stateExact commit and deployed artefactExact prepared state

In detail

Each layer, with the artefact it produces.

The specimens below show the shape of a run state, a verification report and a signed receipt.

Layer 01 — ExecutionAWAITING_VERIFICATION

DoneState

Durable execution and control plane

A run begins with a prose outcome and an explicit authority envelope. DoneState decides whether that run is admissible, holds the lease while it executes, records every transition durably, and stops at AWAITING_VERIFICATION until an independent attestation arrives.

  • Admission control
  • Budgets and leases
  • Idempotency
  • Durable state transitions
DoneState in detailSource
DoneState — run staterun/7c41

  1. ADMITTED

    Outcome accepted inside authority envelope

  2. EXECUTING

    Lease held, budget consuming

  3. VALIDATING

    Local checks and build evidence gathered

  4. AWAITING_VERIFICATION

    Halted — independent attestation required

  5. VERIFIED

    Attestation received, state closed

Layer 02 — VerificationREAD_ONLY

OpsTruth

Independent read-only verifier

OpsTruth reads the system from outside the execution path. It gathers evidence, states plainly what that evidence supports, and refuses to upgrade an absence of evidence into a pass.

  • Repository and stack inspection
  • Tests, build and CI evidence
  • Secrets and configuration checks
  • Routes and runtime evidence
OpsTruth in detailSource
OpsTruth — verification reportread-only
Illustrative OpsTruth verification report showing Verified, Risky and Unproven checks
CheckState

Build reproduces at commit

Artefact matches source tree

verified

Test suite executed

Exit status recorded in CI evidence

verified

No credentials in tracked files

Scan clean at this commit

verified

Declared routes respond

One route returns an error status

risky

Deployed artefact matches commit

No deployment evidence available

unproven
Layer 03 — AuthorisationRECEIPT_SIGNED

AgentProof

Authorised transaction and signed-receipt layer

Before a consequential action runs, AgentProof pins the exact prepared state and the authority that permits it. Execution is exactly-once and recoverable. What comes out is a receipt anyone holding the public key can check.

  • Exact prepared state
  • Exactly-once execution
  • Recovery
  • Independently verifiable receipts
AgentProof in detailSource
AgentProof — signed receiptap1:7c4e9d2b83a15f60c8e7d419ab35f2c0
action
merge_pull_request
prepared state
sha256:9f2c41ab6e0d7c5183ba0e77c4d21f9a
authority
envelope/repo-write@exp-2026-08-29T09:00Z
proposer
agent:coding-harness
executor
agentproof:executor-01
signer
key:ed25519:AP-3f8c
verifier
opstruth:report-2f19
outcome
committed_once

Illustrative specimen. Field values show the shape of a receipt, not a real transaction.

Topology

Where the boundary sits

Execution may act. Verification may only observe. Nothing crosses the boundary in both directions.

Proof & State — system topologyexecution ⟂ verification

Verification side

observes only

  1. Surfaceevidence

    Observable evidence

    Repository at an exact commit, CI output, configuration, routes, runtime and deployment artefacts.

  2. Independent verifieropstruth

    OpsTruth

    Reads only. Classifies each check as Verified, Risky or Unproven.

  3. Outputattestation

    Attestation closes state

    The run closes when an independent attestation says observed state matches the claim.

Self-verification is not proof

Give agents authority. Keep the proof.

Every claim on this site maps to something you can read in the source.

Developer quickstartView on GitHub