zara-memory: reject duplicate recall identities #109

New issue

Closed

opened 2026-09-08 02:02:59 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:02:59 +00:00

Owner

Problem

MemoryService.recall() validates each backend memory independently but currently accepts duplicate stable memory IDs in one result set. That makes provenance/result identity ambiguous and allows a backend to present the same durable identity as multiple records.

Slice

deterministic RED coverage for duplicate backend recall IDs;
reject duplicates after per-record validation and before returning results;
preserve the existing 64-result bound and scope/type/provenance checks;
exact-head compatibility, registry, plugin and Nix gates before merge.

Dependency-ready correctness slice within #7. No parallel memory backend or unsupported recall semantics.

## Problem `MemoryService.recall()` validates each backend memory independently but currently accepts duplicate stable memory IDs in one result set. That makes provenance/result identity ambiguous and allows a backend to present the same durable identity as multiple records. ## Slice - deterministic RED coverage for duplicate backend recall IDs; - reject duplicates after per-record validation and before returning results; - preserve the existing 64-result bound and scope/type/provenance checks; - exact-head compatibility, registry, plugin and Nix gates before merge. Dependency-ready correctness slice within #7. No parallel memory backend or unsupported recall semantics.

nsaspy closed this issue

2026-09-08 02:02:59 +00:00