Durable execution and control plane
AWAITING_VERIFICATIONDoneState
Give the agent room to work without giving up control.
- Outcome
- Authority
- DoneState
- Evidence
- Definition — 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.
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.
ADMITTED
Outcome accepted inside authority envelope
EXECUTING
Lease held, budget consuming
VALIDATING
Local checks and build evidence gathered
AWAITING_VERIFICATION
Halted — independent attestation required
VERIFIED
Attestation received, state closed
Illustrative run states. A run halts at AWAITING_VERIFICATION because DoneState has no authority to close itself.
Capabilities
What DoneState does
Each capability exists to make one class of failure impossible to hide.
- Admission control
- A run is admitted only if the requested outcome fits inside the declared authority envelope. Out-of-envelope work is refused up front, not negotiated mid-run.
- Budgets and leases
- Each run holds a lease with an expiry and a budget ceiling. A lost lease stops execution rather than allowing two workers to act on the same state.
- Idempotency
- Operations carry idempotency keys so a retried or replayed step converges on the same result instead of duplicating side effects.
- Durable state transitions
- Every transition is written before the effect it describes, so the recorded state is never ahead of reality.
- Crash recovery
- After a crash, a run resumes from its last durable state. Recovery is deterministic: the same recorded history produces the same resumption.
- Audit evidence
- The run history is the audit trail — inputs, authority, transitions and outcomes — readable after the agent session is gone.
- Harness-agnostic
- DoneState governs the run, not the model or the editor. The coding harness is a replaceable component.
Explicit limits
What DoneState does not do
Stated limits are part of the design. A component that could do everything could not be trusted to judge anything.
- Does not verify its own work
- Does not close a run on an agent's self-report
- Does not act outside the declared authority envelope
Lifecycle
A run is a durable object, not a session.
Admission, lease, budget and state transitions are recorded before, during and after the agent does anything. If the process dies, the record survives it.
$ donestate run --outcome ./outcome.md --envelope ./authority.jsonADMITTED outcome fits declared envelopeEXECUTING lease held · budget 12/40 tool callsVALIDATING local checks and build evidence gatheredAWAITING_VERIFICATION halted — independent attestation required# DoneState will not transition to VERIFIED on its own.Endpoints
Where DoneState runs
These are the canonical addresses for the live service and its MCP endpoint. Any other hostname you may have seen is historical and is not canonical.
- Live service
- https://donestate.proofandstate.com
- MCP endpoint
- https://donestate.proofandstate.com/mcp
- Source
- https://github.com/AyobamiH/donestate
- Distribution
- DoneState 0.2.0 is in OpenAI Review. It is not approved and not published to any directory.
Relationships
How this layer relates to the others
Proof & State is one system of three independent layers. Each holds authority the others do not.
Verification
OpsTruth
Verification that holds no power to change what it judges.
Authorisation
AgentProof
Consequential actions leave evidence that outlives the session.
DoneState executes; it cannot verify itself. OpsTruth verifies read-only and never writes. AgentProof authorises consequential actions and signs receipts. The separation is the product.