zara-memory: reject backend-injected facts outside registered schema #141

New issue

Closed

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

nsaspy commented

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

Owner

Follow-up to #7.

MemoryService.recall() validates scope/owner/type isolation, but recalled symbolic facts are currently only checked for being strings. A backend can therefore return a memory of the correct type while injecting a predicate that the registered MemorySchema does not allow.

Acceptance:

deterministic RED proves typed recall rejects backend-injected disallowed predicates;
recalled facts are validated against the registered schema, including executable-control-syntax rejection;
untyped recall still validates each returned memory against its registered type schema rather than trusting backend facts;
no persistence/runtime changes outside lost-rob0t/zara-plugins;
zara-memory tests, registry validator, installed/source compatibility, and nix flake check stay green.

Follow-up to #7. `MemoryService.recall()` validates scope/owner/type isolation, but recalled symbolic facts are currently only checked for being strings. A backend can therefore return a memory of the correct type while injecting a predicate that the registered `MemorySchema` does not allow. Acceptance: - deterministic RED proves typed recall rejects backend-injected disallowed predicates; - recalled facts are validated against the registered schema, including executable-control-syntax rejection; - untyped recall still validates each returned memory against its registered type schema rather than trusting backend facts; - no persistence/runtime changes outside `lost-rob0t/zara-plugins`; - zara-memory tests, registry validator, installed/source compatibility, and `nix flake check` stay green.

nsaspy closed this issue

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