What is actually known

A status page that invents green ticks is exactly the failure mode this project exists to argue against. Here is what can honestly be said.

DoneState live service: https://donestate.proofandstate.com with an MCP endpoint at https://donestate.proofandstate.com/mcp. No availability figures are published for it.
OpsTruth: https://opstruth.io with an MCP endpoint at https://mcp.opstruth.io/mcp. The verifier itself runs in your environment via npx opstruth.
DoneState 0.2.0: DoneState 0.2.0 is in OpenAI Review. It is not approved and not published to any directory. Review status is not an approval, a listing or an availability commitment.
Maintenance canary: The current PR-only maintenance canary is AWAITING_VERIFICATION. The independent result is uncertain, so it is not reported as verified.
Managed operation: None. The tooling runs in your environment, against your repositories, under your credentials.
Uptime reporting: Not applicable. There is no monitored service endpoint to report availability for, so no figures are published.
Release status: No releases have been recorded on the changelog. The repositories are the authoritative record of current state.
This website: A static site. If you can read this page, it is serving.

Layers

Where to check each layer

Commits, issues and tags in each repository describe real state better than any summary here could.

DoneState
Durable execution and control plane
github.com/AyobamiH/donestate
OpsTruth
Independent read-only verifier
github.com/AyobamiH/opstruth
AgentProof
Authorised transaction and signed-receipt layer
github.com/AyobamiH/agentproof

If a hosted component is ever operated, this page will carry real monitoring data and say where it comes from. Until then see the changelog.

An honest unknown is more useful than a confident green tick.