GitLab Transcend · Evidence, not assurances

Did deleted data come back?

AfterDelete runs deterministic erasure-race rehearsals and checks supported database destinations directly. It does not claim universal erasure.

Release decisionPASS
Current-source tests passed5/5
Undeclared destinations0

Replayed scenarios

ExecutionScenarioResultCopy rowsVector rowsWorker outcomes
Reference Unsafequeued_job_after_deleteFAIL11materialized
Reference Unsafelate_retry_with_old_payloadFAIL11materialized, materialized
Reference Unsafestale_snapshot_rebuildFAIL11materialized
Reference Unsafevalid_index_then_erasePASS00—
Reference Unsafeunrelated_changePASS00—
Reference Safequeued_job_after_deletePASS00deletion_barrier
Reference Safelate_retry_with_old_payloadPASS00deletion_barrier, deletion_barrier
Reference Safestale_snapshot_rebuildPASS00deletion_barrier
Reference Safevalid_index_then_erasePASS00—
Reference Safeunrelated_changePASS00—
Current Sourcequeued_job_after_deletePASS00deletion_barrier
Current Sourcelate_retry_with_old_payloadPASS00deletion_barrier, deletion_barrier
Current Sourcestale_snapshot_rebuildPASS00deletion_barrier
Current Sourcevalid_index_then_erasePASS00—
Current Sourceunrelated_changePASS00—

Code destinations examined

FileLineDestinationDecision
src/afterdelete/cli.py98search_indexPASS
src/afterdelete/integrations.py7search_indexPASS
src/afterdelete/integrations.py11analytics_cachePASS

Release assessment

No blocking findings

Proof boundary: Named sinks in this application, synthetic records and known delayed-event sequences. External replicas, hidden SDK calls, backups and legal obligations are outside this automated check.