Skip to content

Accountability infrastructure for autonomous engineering

DoneState documentation

Guides, concepts, complete references, security boundaries, and operating help.

Hosted liveSource

DoneState docs / Limits & status

Current boundaries are part of the product contract

This page separates what the owned service can do from what external distribution channels have approved or published.

Owned service liveExternal listings separate

Public interface versions

Hosted MCP
Server version 0.3.0 on the canonical owned endpoint, with 20 current tools.
CLI package
Published npm package version 0.1.2, with nine current commands plus help aliases.
Verification contract
New hosted objectives use donestate.verification-contract.v2 complete verifier responses.

Hosted objective limits

Acceptance criteria
1 to 20 entries; each up to 2,000 characters.
Verification requirements
Up to 100 requirements.
Trusted verifier fingerprints
Up to 20 SHA-256 fingerprints.
Changed files
Objective budget from 1 to 500; default 100.
Duration
60 seconds to 2 hours; default 30 minutes.
Maintenance required checks
Up to 20 exact check names.

Capabilities DoneState does not currently claim

Autonomous merge of its own pull requests
Autonomous deployment or release publication
Multi-repository objectives
Repository-fleet authority
A failed workflow as automatic repair authority
Self-verification of its own execution

Distribution channels

Owned Proof & State service
First-class hosted launch channel at donestate.proofandstate.com. It does not wait on an external directory to exist.
OpenAI / ChatGPT
DoneState 0.3.0 remains a separate provider-review channel in the latest repository evidence. Review is not publication.
GitHub Marketplace
The listing remains a separate provider-review channel in the latest repository evidence. Owner preview state is not public discoverability.

Standalone account controls

The production service includes an authenticated account-console path through the existing credential-settings flow. It exposes customer-visible credential, selected-repository, and indexed-run state and a fail-closed deletion path.

Broad self-serve acceptance is still tracked separately from the existence of the live hosted runtime. Historical direct objectives created before owner-level indexing can require deletion by known run ID or a privacy request.

Source-of-truth links