---
id: TST-PFM-DJE-017
title: Hard delete
kind: unit
product_area: platform
module: data-job-engine
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/data-jobs/src/hard-delete.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: In-memory fixtures and restored dependency doubles.
evidence:
  - 'macroservice-libraries:packages/data-jobs/src/hard-delete.spec.ts'
assertion_inventory:
  - the text a person types to confirm a hard delete
  - 'names the records by the object type, which is where the one definition of the label lives'
  - 'reads an underscored name as the words it is, because a person types words'
  - 'takes the whole name when the type names no service, rather than answering nothing'
  - counts the records the validation said it would delete
  - counts the reversible records of a rollback that compensates by deleting what a job created
  - prefers what the impact says it would delete to anything else it counted
  - 'counts none when the impact counted none, so the text is still a sentence a person can be shown'
  - 'accepts exactly that text, and the whitespace a form field leaves around it'
  - >-
    refuses a different count, a different object and a different case, which is the whole point of
    typing it
  - a record the domain blocks only at apply time
  - >-
    is that item's conflict in a delete's apply, because the validation had already reported the
    blocked records
  - 'is still blocked in a delete''s validation, which is the run whose whole job is to report it'
  - 'is left alone for every other operation, where blocked means a dependency and not a race'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Hard delete

## Verification Boundary

The suite checks an isolated production calculation, declaration or adapter. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise hard delete. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

An isolated check does not establish a deployed workflow, database enforcement or complete feature acceptance.

## Real Dependencies and Test Doubles

The production function or declaration is exercised with in-memory inputs and dependency doubles. This boundary does not require a live database.

## Must Not Be Doubled

The production function under examination and its returned decisions remain real; replacing their answers defeats the check.