zara-memory: enforce backend memory-type isolation #147

New issue

Closed

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

nsaspy commented

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

Owner

Parent

Advances #7.

Problem

MemoryService validates backend scope/owner isolation, but a backend result can report a different type than the registered/requested schema. That breaks the plugin-specific schema boundary: a write or filtered recall can silently cross memory types even though scope ownership remains correct.

Slice

deterministic tests for mismatched backend type on remember and typed recall;
require backend results to match the requested memory type whenever a type was explicitly requested;
keep untyped recall behavior unchanged;
no symbolic-memory backend feature invention.

Verification

Plugin tests, registry validator, and nix flake check.

## Parent Advances #7. ## Problem `MemoryService` validates backend scope/owner isolation, but a backend result can report a different `type` than the registered/requested schema. That breaks the plugin-specific schema boundary: a write or filtered recall can silently cross memory types even though scope ownership remains correct. ## Slice - deterministic tests for mismatched backend type on remember and typed recall; - require backend results to match the requested memory type whenever a type was explicitly requested; - keep untyped recall behavior unchanged; - no symbolic-memory backend feature invention. ## Verification Plugin tests, registry validator, and `nix flake check`.

nsaspy closed this issue

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