Open source
Claims should be checkable.
A system whose entire argument is independent verification cannot ask you to take its own description on faith. The repositories are the evidence for everything written on this site.
- DoneState
- OpsTruth
- AgentProof
Repositories
Three repositories, three boundaries
Execution
DoneState
DoneState is the durable execution and control plane for autonomous coding work: it accepts an outcome plus an authority envelope, enforces admission, budgets, leases and idempotency, records durable state transitions and audit evidence, recovers deterministically from crashes, and cannot verify its own work.
github.com/AyobamiH/donestateVerification
OpsTruth
OpsTruth is an independent read-only verifier for AI-assisted engineering: it inspects repository, stack, test, build, CI, secrets, configuration, route, runtime and deployment evidence, separates findings into Verified, Risky and Unproven, and performs no write actions of any kind.
github.com/AyobamiH/opstruthAuthorisation
AgentProof
AgentProof is the transaction and signed-receipt layer for consequential agent actions: it binds authority to an exact prepared state, executes exactly once with recovery, and emits an independently verifiable signed receipt, keeping proposer, authority, executor, signer and verifier separate.
github.com/AyobamiH/agentproof
Distribution
What is published, and what is not.
OpsTruth is invoked as npx opstruth. DoneState is installed as a global package. AgentProof is read and built from source; this site does not claim a package publication for it.
Licensing, versioning and support expectations live in each repository. Where this page and a repository disagree, the repository is authoritative.
The canonical governance repository for the Proof & State system and this website is github.com/AyobamiH/proof-and-state.
$ npx opstruth# read-only verifier · no writes$ npm install -g donestate# durable execution and control plane$ git clone https://github.com/AyobamiH/agentproof# source and release candidates; no npm publication claimedContributing
Where a contribution helps most.
Verification surfaces are the highest-leverage area: each new surface turns something currently Unproven into something that can be classified.
Adversarial reading of the boundary is equally valuable. If you find a path where execution can influence a verdict, that is a defect in the architecture, not a feature request.
Open an issue or a pull request on the relevant repository.
Give agents authority. Keep the proof.
Read the source before believing the site.