Delete brand binding

Outcome

Remove one consumer binding.

Before you start

• Verify whoami and the pinned credential context, then inspect the exact discovered action before preparing input.
• Discover a granted Brand workspace. Pass its resourceType/workspace identifier separately from input; a copied fixture identifier grants no access.
• The declared permission is brand:write. The active credential, application scope, resource binding and runtime authority must all authorize the request.
• Review the exact mutation and recovery, including destructive scope, and execute only after the intended effect is authorized.

Discover the target

topolo whoami --json
topolo actions get app_topolo_brand.brand_bindings.delete --detail --json
topolo resources topolo-brand --json
topolo workspaces list topolo-brand --json

Request

DELETE /api/brand-bindings/{id}

Resource context is the selected Brand workspace. CLI/SDK action input includes path identifiers; direct HTTP JSON bodies exclude path parameters. Read the reviewed plan for the exact request.

Input fields

Exact published input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "description": "Exact kit or binding identifier from the corresponding list action; its meaning is determined by this action."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Effects

Deletes the exact binding in the selected workspace and records an audit. Kits and snapshots remain.

Interpret the response

deleted:true confirms removal. Contextual resolution can then choose a less specific eligible binding; deletion does not necessarily mean the consumer has no brand.

Response identifier contract:

{
  "kind": "brand_bindings_delete",
  "identifierSource": "none",
  "explanation": "deleted:true confirms removal. Contextual resolution can then choose a less specific eligible binding; deletion does not necessarily mean the consumer has no brand."
}

Worked examples

These complete synthetic responses were captured from the local worker over canonical SQL migrations. Auth and R2 dependencies are simulated; notification delivery is not exercised. Set BRAND_WORKSPACE_ID from granted workspace discovery. Save reviewed input as payload.json, validate and inspect the unchanged plan. The final mutation command and MCP confirm flag assume the intended effect has already been authorized.

Minimal example

Input · payload.json:

{
  "id": "brand_binding_a4ab1e79-6dbe-45c4-af96-093a041abde6"
}

CLI:

topolo actions validate app_topolo_brand.brand_bindings.delete --data @payload.json --json
topolo actions plan app_topolo_brand.brand_bindings.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_brand.brand_bindings.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_brand.brand_bindings.delete",
    "input": {
      "id": "brand_binding_a4ab1e79-6dbe-45c4-af96-093a041abde6"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "deleted": true
}

deleted:true confirms removal. Contextual resolution can then choose a less specific eligible binding; deletion does not necessarily mean the consumer has no brand.

Workflow example

Input · payload.json:

{
  "id": "brand_binding_813652d7-03ee-4cb3-b08c-001b1ba912f1"
}

CLI:

topolo actions validate app_topolo_brand.brand_bindings.delete --data @payload.json --json
topolo actions plan app_topolo_brand.brand_bindings.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_brand.brand_bindings.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_brand.brand_bindings.delete",
    "input": {
      "id": "brand_binding_813652d7-03ee-4cb3-b08c-001b1ba912f1"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "deleted": true
}

deleted:true confirms removal. Contextual resolution can then choose a less specific eligible binding; deletion does not necessarily mean the consumer has no brand.

Verify the result

List bindings and resolve the intended context to confirm the new winning scope or absence.

Errors and recovery

refused · HTTP 404

{
  "input": {
    "id": "missing-binding"
  },
  "response": {
    "error": "brand_binding_not_found"
  }
}

• auth_error (HTTP 401): CLI/SDK authentication classification when Auth returns a non-code message: restore the authorized credential, then verify whoami and context. Preserve the exact service message.

• permission_denied (HTTP 403): Use the exact permission and granted resource required by the reviewed action; organization membership alone is insufficient.

• workspace_required (HTTP 400): Discover and select a granted Brand workspace before preparing the request.

• brand_storage_unavailable (HTTP 503): The Brand storage bindings are unavailable. Preserve the request identifier and report the service fault; do not retry an unverified mutation.

• brand_binding_not_found (HTTP 404): Discover the exact parent/resource again and inspect its lifecycle status. Missing, inaccessible or immutable resources can share this refusal.

Recovery boundary

Capture the complete prior tuple and kit, then review an upsert restoring equivalent semantics. A recreated binding need not retain its previous identifier.

Related actions

• app_topolo_brand.brand_bindings.list: List consumer bindings for kits in the selected workspace.
• app_topolo_brand.brand_kits.resolve_context: Resolve the first eligible brand for a consumer context.

Evidence

Four real local SQLite stores use all canonical migrations; Auth identity/grants and archival plus R2 object storage are explicitly simulated. Notifications are disabled in fixtures. No notification delivery, live mutation, gateway credential parity or deployed environment proof is claimed. Fixture identifiers and timestamps are synthetic and must be replaced by exact authorized resource discovery.