WorkspaceLifecycleRequest

The one destructive workspace operation's body.

The consequence is presented by the caller and accepted before this is sent (rev 4 §4.2 step 2, S13). What crosses is the acceptance: the token the gateway issued alongside the consequence it computed, round-tripped unchanged - see [WorkspaceConfirmation].

It is still not a credential: the scope is what authorizes the operation. What the token adds is that the acceptance is about something. A token the gateway does not recognise, one issued for another workspace or another action, one already spent, or one that has expired is refused before anything is closed.

Type object

Shape

Field	Type	Description
actionrequired	WorkspaceLifecycleAction	What `POST /v1/workspaces/{id}/lifecycle` is being asked to do. Three verbs, and no permanent delete. There is no purge route anywhere in Koru - the retention sweep is the only thing that removes bytes - so naming one here would be describing an operation that does not exist.
confirmationrequired	string
replacement_name	string	Localized default for a required replacement. Older callers use the protocol's English fallback; this is not a second creation operation. Default `"My Workspace"`
removal_attempt	RemovalAttemptId or null

Example

{
  "action": "archive",
  "confirmation": "string",
  "replacement_name": "My Workspace",
  "removal_attempt": "00000000-0000-4000-8000-000000000000"
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Used by

POST/v1/workspaces/{id}/lifecycle
Archive, soft-delete or restore a workspace, closing its terminals first

Generated from contract version 1. Last updated November 12, 2026.