---
title: "Verify source deletions synchronize without resurrection"
description: "Check an owned sandbox integration deletion event, confirming the destination follows its retention policy and later sync cannot recreate the removed source."
canonical_url: "https://vostride.com/agent-library/integrations-sync/deleted-source-tombstone.md"
md_url: "https://vostride.com/agent-library/integrations-sync/deleted-source-tombstone.md"
content_kind: "recipe"
topic: "integrations-sync"
---

# Verify source deletions synchronize without resurrection

Check an owned sandbox integration deletion event, confirming the destination follows its retention policy and later sync cannot recreate the removed source.

## Risk

Deletions need durable identity information because the source record may no longer be fetchable. Test the delete event followed by a normal reconciliation cycle to expose tombstones that are forgotten or treated as missing data.

## Fixtures

- An owned sandbox source and destination with a single previously synchronized disposable record and captured mapping identifiers.
- An external source fixture that deletes the record and delivers its documented deletion event, plus a normal subsequent sync checkpoint.
- A read-only destination and tombstone oracle and an explicit product policy for archive, removal, or retained historical content.

## Steps

1. Open the destination record and verify its source mapping and original active state before deletion.
2. Run the external deletion fixture and verify integration activity references the intended source identifier.
3. Verify the destination transitions to the documented archived, removed, or historical state without affecting an unrelated control record.
4. Complete another normal sync cycle and inspect the independent oracle; verify the deleted source remains represented by the intended terminal mapping and the destination is not recreated.

## Expected results

- The destination applies the documented deletion-retention policy to the correct record.
- The deletion identity survives the following reconciliation cycle.
- No new active destination copy or unrelated control change appears.

## False-pass traps

- Checking only immediately after a delete event misses resurrection during the next full sync.
- A missing source API response can be an outage rather than a confirmed deletion event.

## Cleanup

- Remove residual sandbox tombstones and restore the disposable source only through the test fixture if needed.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Integration and synchronization QA recipes](/agent-library/integrations-sync.md)
- [Software factory QA library](/agent-library.md)