Developers
Start with the verifier.
The fastest way to understand Proof & State is to point a read-only verifier at a codebase you already have opinions about, and see which of those opinions it can actually evidence.
- Install
- Verify
- Read report
$ npx opstruthread-only inspection · no writes performedWhere to go
Four entry points
Quickstart
Run the read-only verifier against a repository you already trust and read the report.
Integrations
How the layers sit alongside an existing coding harness and CI setup.
Documentation
Reference index: concepts, models and where each detail is authoritative.
Open source
Repositories, licensing and how to read the implementation.
Commands
What each layer looks like from a terminal
Distribution differs per layer. Where a package is not published, the repository is the source of truth.
$ npx opstruthverified / risky / unproven report# read-only — never writes$ npm install -g donestate$ donestate run --outcome ./outcome.md# halts at AWAITING_VERIFICATION$ git clone https://github.com/AyobamiH/agentproof# read from source; no package publication is claimedSource
Repositories
DoneState
Durable execution and control plane
github.com/AyobamiH/donestateOpsTruth
Independent read-only verifier
github.com/AyobamiH/opstruthAgentProof
Authorised transaction and signed-receipt layer
github.com/AyobamiH/agentproof
These are ecosystem targets and compatible workflows. Naming a harness is not a claim of partnership, endorsement, certification or affiliation.
Give agents authority. Keep the proof.
Run the verifier before you trust anything written on this site.