Erase workspace privacy data

Outcome

Permanently erase Brand data and stored asset objects for the selected workspace.

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 workspace:delete. 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.privacy.delete --detail --json
topolo resources topolo-brand --json
topolo workspaces list topolo-brand --json

Request

DELETE /api/privacy

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

Use {} as input; credential and workspace resource context remain separate.

Exact published input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Effects

Deletes the selected workspace kits, versions, bindings, audits, asset rows and original/frozen asset objects. Workspace identity is retained; other workspaces are outside this deletion scope.

Interpret the response

recordsDeleted and objectsDeleted report the SQL rows and object keys processed. They are not organization-wide totals or a claim of a distributed transaction. A repeat can return zero.

Response identifier contract:

{
  "kind": "workspace",
  "identifierSource": "response",
  "idPath": "$.workspaceId"
}

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:

{}

CLI:

topolo actions validate app_topolo_brand.privacy.delete --data @payload.json --json
topolo actions plan app_topolo_brand.privacy.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_brand.privacy.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.privacy.delete",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "organizationId": "org_documentation_fixture",
  "workspaceId": "ws_brand_documentation_fixture",
  "recordsDeleted": 15,
  "objectsDeleted": 2
}

recordsDeleted and objectsDeleted report the SQL rows and object keys processed. They are not organization-wide totals or a claim of a distributed transaction. A repeat can return zero.

Workflow example

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_brand.privacy.delete --data @payload.json --json
topolo actions plan app_topolo_brand.privacy.delete --resource-type workspace --resource-id "$BRAND_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_brand.privacy.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.privacy.delete",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "organizationId": "org_documentation_fixture",
  "workspaceId": "ws_brand_documentation_fixture",
  "recordsDeleted": 18,
  "objectsDeleted": 4
}

recordsDeleted and objectsDeleted report the SQL rows and object keys processed. They are not organization-wide totals or a claim of a distributed transaction. A repeat can return zero.

Verify the result

Read privacy.export for the same workspace and require empty kit, version, binding and asset arrays. Verify previously retained asset URLs separately; preserve the request and exact result after any partial failure.

Errors and recovery

• 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.

Recovery boundary

Brand provides no recovery of erased records or bytes. Export and download needed assets before authorized erasure; do not blindly retry an unknown outcome.

Related actions

• app_topolo_brand.privacy.export: Export records and asset download paths belonging to the selected Brand workspace.
• app_topolo_brand.workspaces.delete: Archive an empty Brand workspace through the platform workspace authority.

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.