DoneState docs / Understand
Account and data lifecycle
DoneState keeps identity, execution funding, repository selection, objective state, and verification evidence separate. This page describes the public customer-visible lifecycle rather than private infrastructure implementation detail.
Identity
Hosted users authenticate through GitHub OAuth. DoneState associates user-controlled service state with the authenticated GitHub login used for that connection.
A GitHub identity is not itself an execution budget or mutation authority. Credential state, repository access, and objective authority remain separate checks.
OpenAI execution credential
A hosted user can connect a user-funded OpenAI API key through a short-lived HTTPS settings flow created by create_openai_credential_setup.
DoneState stores the credential encrypted at rest and exposes only non-secret status information such as connection state and a short fingerprint. The key is not returned by get_openai_credential_status.
delete_openai_credential({ "confirm": true })Selected repository state
Maintenance selection records the repository, default branch, observation or PR-only mode, scheduling flag, automatic-repair flag, installation association where present, and exact required check names.
Removing a repository from DoneState maintenance deletes that selection and its related maintenance findings from the DoneState registry. It does not uninstall the GitHub App.
remove_maintenance_repository({ "repository": "owner/name", "confirm": true })Objective state and receipts
A hosted objective records the bounded objective, durable run state, action intents and settlements, event history, publication references, and verification material needed to recover and explain what happened.
Eligible terminal or cancelled objectives can be deleted by run ID. Active work must first reach a state in which deletion is safe.
delete_objective({ "runId": "11111111-1111-4111-8111-111111111111" })Verification evidence
Verification material can include the sealed subject, acceptance requirements, execution snapshot digest, nonce, requirement results, evidence references, and signed independent attestation. Its purpose is to let a reviewer distinguish implementation activity from independently supported claims.
Public documentation intentionally describes the contract and semantics without publishing private operational credentials or secrets.
Current deletion model
Credential
Self-service through delete_openai_credential when no active run is holding the execution credential.
Objective
Self-service through delete_objective for eligible terminal, cancelled, or verification-waiting objective state.
Maintenance selection
Self-service through remove_maintenance_repository for the selected repository and its maintenance findings.
Retention and external systems
Deleting DoneState service state does not erase independent records already created in GitHub, such as commits, branches, pull requests, workflow runs, or repository audit history. Those records are controlled by GitHub and the repository owner.
Likewise, model-provider usage records associated with a user-funded OpenAI account are controlled by that provider, not by DoneState.