Skip to main content
The one physical deletion tckg does. Blocks are never deleted one by one (see Delete a memory); a whole tenant is, when the customer deleted the collection it stood for. Everything the tenant has goes in one transaction: nodes, edges, verdicts, anchors, fact declarations and backfill batches. Other tenants are untouched. The server records that it happened. A later read for the same tenant name carries forgotten in its certificate, with when and how many rows, so a certificate never claims a scope that was emptied is one that was always empty.

Request

The route is on only when the deployment sets TCKG_FORGET=1; otherwise it answers 501. The API key selects the tenant, as everywhere, and the body has to name the same tenant: a key can forget only its own tenant, and only when it says so twice.
string
required
The tenant to forget. Must be the key’s tenant, or the request is 403 TCKG_TENANT_MISMATCH.

Response

object
Rows deleted per table: nodes, edges, verdicts, anchors, facts, batches.
A tenant with no rows is 400 TCKG_TENANT_EMPTY. If anything fails midway the transaction rolls back: the ledger’s guards are back up and every row is still there.
This cannot be undone. Take a database backup before forgetting a tenant you might need again.