Relation Integrity Guardian — Soft Delete Safety, Cascade Rules & AI Dependency Resolver

[Weegy]

Competitor Context

Payload CMS Issue #16022 (March 21, 2026, triaged as Bug) exposes a dangerous soft-delete integrity flaw:

When trash: true is enabled on a collection, items can be trashed (soft-deleted). However, relationship fields from other collections still return the IDs of trashed entries — making them appear as partial/broken relation objects in API responses. Example: {writers: {docs: [1, {id: 2, name: "Active Writer"}]}} where ID 1 is a trashed entry leaking into the API.

This is a data exposure and integrity failure. API consumers receive ghost IDs that resolve to nothing, causing null-pointer errors in frontend apps and potentially exposing internal database IDs of "deleted" content.

Strapi has had similar relation consistency bugs (e.g., #25780 — releases failing on out-of-sync relations, #25790 — permission inconsistency on relation fields). Data integrity across relations is an unsolved problem for every major CMS.

The Numen Opportunity

Numen can build first-class relation integrity with AI-assisted dependency resolution — a feature that no competitor has shipped systematically.

Proposed Feature: Relation Integrity Guardian — Soft Delete, Cascade Rules & AI Dependency Resolver

Core behavior:

• When content is trashed/soft-deleted, all relation references are updated atomically:
  • Cascade nullify: relation becomes null (API-safe)
  • Cascade remove: relation entry removed from arrays/joins
  • Cascade restrict: prevent deletion if dependencies exist (with clear error listing dependents)
  • Cascade replace: AI suggests replacement content before deletion is confirmed

AI Dependency Resolver:
Before confirming a soft-delete, Numen surfaces:

• "This content is referenced by 12 pages and 3 content items"
• AI suggests: "Replace with similar content: [list of candidates from knowledge graph]"
• One-click bulk re-reference: swap all references to the trashed item to a chosen replacement

Relation Health Monitor:

• Background job detects orphaned relations (references to deleted/missing content)
• Dashboard widget showing "12 broken relations detected" with AI-suggested fixes
• API responses NEVER return partial ghost IDs — always resolved or null

Garbage Collection:

• Scheduled cleanup of long-trashed items after configurable retention period
• Pre-cleanup report: what will be purged and what depends on it
• AI summary: "Purging 847 items. 3 active pages reference trashed content — review before proceeding."

Numen Edge:
Competitors treat soft-delete as a database-level flag with no relation awareness. Numen makes content lifecycle a first-class, relation-aware system with AI acting as a dependency manager. This is critical for enterprise teams managing thousands of content items with complex relation graphs.

Scope: M
Priority: HIGH — Real data integrity risk in competitors; positioning opportunity for enterprise trust

Signal source: Payload #16022 (March 21, 2026) + Strapi #25780/#25790 (ongoing relation integrity failures).