We are building a proper deletion feature inside Enate — one that is safe, controlled, and leaves a clear A safe, auditable, and compliant way to permanently delete packet data from every system Enate holds data in. Today this is done via manual SQL scripts — which is slow, risky, and leaves no audit trail. This epic replaces that entirely with a structured, two-person approved, multi-system deletion framework. The is split into 5 features that are built and delivered in sequence. Each feature is independent enough to be built by a separate team but they all connect together into one end-to-end flow. Phase 1 lays the foundation. It builds the backend deletion engine that every other part of this capability depends on, and adds deletion support to Intelligent Search (ITGS) — which ships in the July Alpha and cannot go live without deletion parity. Without Phase 1 complete, nothing in Phase 2 can be built or tested. These two features are the critical path for the entire deletion programme. What is being built in Phase 1: Feature 1 — Packet Group Deletion Engine The core backend engine. When given a list of packet references, it resolves the full group of related packets (parent + all children), validates eligibility, and orchestrates deletion across every system Enate holds data in — in the correct order. This engine is the foundation every other feature in both Phase 1 and Phase 2 calls into. Nothing works without it. Feature 2 — Intelligent Search (ITGS) Deletion Today, ITGS receives create and update events from Core but has no deletion support. If a packet is deleted from Core, it stays indexed and searchable in ITGS — a direct data violation. This feature adds a deletion event listener to ITGS, removes the corresponding index entry, and sends a positive confirmation back to Core before Core removes its own records. ITGS ships in the July Alpha. Deletion support must be ready at the same time. ⚠️ Important — this is infrastructure, not a user-facing feature: Phase 1 delivers no UI. Customers and agents will not see any change in the product when Phase 1 ships. The deletion engine and ITGS integration run entirely in the background. The user-facing deletion experience — the Excel upload, the approval flow, the audit trail — is delivered in Phase 2. This feature will only be available to use after all 5 features across Phase 1 and Phase 2 are complete. Packet Group Deletion Engine- [ https://feedback.enate.net/feature-request/p/packet-group-deletion-engine ] Intelligent Search (ITGS) Deletion- [ https://feedback.enate.net/feature-request/p/intelligent-search-itgs-deletion ] This is Phase 1 of 2. See the full picture in Data Deletion Purge packet— Phase 2: Warehouse, Marketplace & Excel UI [ https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework-phase-2 ]
