ackDB

Delete a human (company timelines keep their evidence)

Hard-deletes the person, archived and restorable, with their durable keys frozen as a tombstone.

Events are DETACHED, never deleted. A Slack message in a customer's channel is that COMPANY's history — deleting the human must not rewrite it. Every person_id/contact_id pointer is nulled and archived, so a restore re-attaches them. Embedding chunks and conversations are untouched: the text did not change, only its attribution.

Goes: the person row, its durable keys, person attributes, merge candidates naming it, its merge tombstones, every affiliation edge (with links, traits and relationship ownership), and its segment memberships (each preceded by an exit).

delete/api/v1/ackdb/persons/{personId}

Request

  • Base URL
    http://localhost:3009
  • Auth
    HTTP bearer

Path parameters

personIdstring required

Person id (ULID).

Query parameters

dryRunboolean

Preview only. Runs the IDENTICAL resolution, cascade and reporting, then rolls back — so the preview is produced by the code that does the work, not by a second implementation that can drift.

Request body

reasonstring

Why — stored on the archive header.

actorstring

Who — console user email; null for service calls.

dryRunboolean

Same as ?dryRun=true, for clients that cannot send query params.

Response

Deleted (or previewed). Returns what was deleted, what was detached, what was deliberately retained, and the tombstone that now guards the record's identifiers.

Changes

No recorded changes to this operation across all 1 revision of this API.