zara-memory: reject duplicate projection cleanup identities #106

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.forget() bounds and validates backend projection_ids, but accepts duplicate IDs. Duplicate cleanup identities make deletion evidence ambiguous and can hide a backend that reports repeated cleanup instead of distinct projections.

Slice

deterministic RED coverage for duplicate projection cleanup IDs;
reject duplicates after shape/bound validation;
preserve existing 64-ID and 128-character bounds;
exact-head compatibility, registry, plugin and Nix gates before merge.

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

## Problem `MemoryService.forget()` bounds and validates backend `projection_ids`, but accepts duplicate IDs. Duplicate cleanup identities make deletion evidence ambiguous and can hide a backend that reports repeated cleanup instead of distinct projections. ## Slice - deterministic RED coverage for duplicate projection cleanup IDs; - reject duplicates after shape/bound validation; - preserve existing 64-ID and 128-character bounds; - exact-head compatibility, registry, plugin and Nix gates before merge. Dependency-ready correctness slice within #7. No parallel memory backend or unsupported forgetting semantics.

nsaspy closed this issue

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