zara-memory: bound backend recall result cardinality #115

New issue

Closed

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

nsaspy commented

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

Owner

Problem

MemoryService.recall() currently accepts any backend list length and validates every returned item. A malformed or hostile backend can therefore return an unbounded result set, defeating the plugin's bounded-runtime/memory posture even though write-side fact collections are capped.

Slice

add deterministic RED coverage proving oversized recall result sets fail closed;
enforce a fixed service-level recall-result bound before per-item validation;
keep behavior structured and backend-agnostic;
run focused tests, registry/compatibility gates, and Nix checks before merge.

This is a dependency-ready correctness slice within #7 and does not emulate missing symbolic-memory search/forget capabilities.

## Problem `MemoryService.recall()` currently accepts any backend list length and validates every returned item. A malformed or hostile backend can therefore return an unbounded result set, defeating the plugin's bounded-runtime/memory posture even though write-side fact collections are capped. ## Slice - add deterministic RED coverage proving oversized recall result sets fail closed; - enforce a fixed service-level recall-result bound before per-item validation; - keep behavior structured and backend-agnostic; - run focused tests, registry/compatibility gates, and Nix checks before merge. This is a dependency-ready correctness slice within #7 and does not emulate missing symbolic-memory search/forget capabilities.

nsaspy closed this issue

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