A contributor found the live twin of a namespace bug I’d filed as low priority

Description and use

In YantrikDB, cross‑namespace redundancy triggers exposed full texts from different users. The fix scopes checks per namespace and drops cross‑namespace triggers, preventing privacy leakage.

Problem

Cross‑namespace redundancy triggers were being logged, exposing full memory texts from different users in a single store.

Outcome

Implemented namespace‑aware redundancy checks and a write‑path gate that removes cross‑namespace triggers, eliminating privacy leakage while preserving legitimate intra‑namespace redundancy detection.

Workflow

• 1. Query distinct namespaces of active memories with embeddings.
• 2. For each namespace, run redundancy check with a namespace filter.
• 3. Resolve source RIDs for each trigger and drop those spanning multiple namespaces before persisting to trigger_log.

Evidence

The redundancy check now first runs SELECT DISTINCT namespace FROM memories WHERE consolidation_status = 'active' AND embedding IS NOT NULL

Source

drop_cross_namespace_triggers resolves the namespace of every source_rid on each trigger and drops, with a tracing::warn!, any trigger whose rids land in more than one namespace

Source