Integrations and connection boundaries

The hosted service is exposed as remote HTTP MCP at https://donestate.proofandstate.com/mcp. A client needs remote HTTP MCP support and must be able to complete the service OAuth flow.

The protocol surface is client-neutral. A client that has not been accepted end to end should still be treated as a new integration until authentication, tool discovery, browser handoff, and consequential tool calls have been exercised safely.

Normal hosted users authenticate with GitHub. OAuth provides user identity and the repository access available to that identity for the direct public-repository path.

OAuth repository access is capability, not standing authority. DoneState still requires an explicit objective and consequence classes before it may write, commit, push, or open a pull request.

Private-repository execution and scheduled maintenance use a selected GitHub App installation rather than broadening the normal OAuth path. Repository selection can be observe or pr_only.

Installing the App does not automatically authorise repair. Automatic maintenance also requires repository selection, scheduling, PR-only mode, exact required checks, and an eligible finding.

Hosted implementation uses the user's own OpenAI API credential. The secret is entered through a short-lived DoneState HTTPS setup flow, encrypted at rest, and never returned through MCP status responses.

The credential funds coding-model execution; it does not grant repository authority. GitHub access and DoneState consequence authority remain separate gates.

CI is external evidence about a published head. For maintenance automation, configured exact check names can become machine-checkable verification requirements.

A failed workflow alone is not permission to repair code. DoneState can record it as a maintenance finding, but repair eligibility comes from the explicit maintenance policy and admitted issue path.

OpsTruth is the independent verifier in the current production proof chain. DoneState seals the subject and requirements; OpsTruth observes them and returns a versioned report plus signed attestation.

DoneState checks signer identity, nonce, subject binding, report shape, requirement results, and signature. It does not manufacture the verifier decision itself.