Resolve an explicit durable or default Scope binding

POST
/v1/scope-bindings/resolve

Inspect the Server-owned Scope selection for the current host identity before an operation that needs a binding. Reuse the returned Scope. Do not guess a Scope from the repository, branch, directory, or prompt, and do not change bindings while diagnosing availability. No resolvable binding, or an unknown explicit Scope ID, returns 404 scope_not_found. A persisted durable or default binding whose target is missing returns 409 scope_binding_target_missing with details.scope_id. Resolution stops at that binding without falling back or creating a replacement Scope. Operator repair is required; clients must not treat this conflict as an unprovisioned identity.

Authorization

BearerAuth
AuthorizationBearer <token>

Bearer credential resolved to an opaque authenticated Principal by the Server deployment.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/scope-bindings/resolve" \  -H "Content-Type: application/json" \  -d '{}'
{  "scope_id": "string",  "title": "string",  "summary": "string",  "parent_scope_id": "string",  "context_references": [    "string"  ],  "external_references": [    {      "kind": "string",      "value": "string"    }  ],  "version": 1}

Resolve an observation selection to a frozen Scope set POST

Previous Page

Persist an external identity to Scope binding PUT

Bind the host identity to an existing Scope only when the user explicitly requests a work-boundary change. Respect host-controlled identity fields. Do not switch Scope to work around a missing result or failed Memory operation.