Purge Subject Knowledge

POST /knowledge/subject-purge

Erase one person across every knowledge base in the organization (§12).

The one load-bearing line is :func:_organization_anchored. Everything else is the service’s.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — SubjectPurgeRequest

Field	Type		Notes
subject_kind	user | guest	required	—
subject_id	string	required	min length 1 max length 200
reason	string	required	min length 3 max length 2000

Responses

Status	Description	Body
200	Successful Response	PurgeResult
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/knowledge/subject-purge \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "subject_kind": "user",
       "subject_id": "string",
       "reason": "string"
     }'

Response — PurgeResult

Field	Type		Notes
subject_kind	user | guest	required	—
subject_id	string	required	—
actions	PurgeActions	required	—
retained	PurgeRetained	required	—
workspaces_visited	integer	optional	Default 0.