zara-memory: validate schema descriptor types at registration boundary #124

New issue

Closed

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

nsaspy commented

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

Owner

Problem

MemorySchema.__post_init__() assumes its descriptor fields already have the annotated runtime types. Malformed names/scopes/predicate collections can leak raw Python TypeError or create mutable/non-canonical schema descriptors instead of failing at the plugin's schema boundary.

Required behavior

schema name must be non-empty text within the existing 128-character bound;
allowed scopes and fact predicates must be frozenset[str] values with non-empty text entries;
unsupported scopes still fail deterministically;
malformed descriptors raise ValueError, never incidental Python type errors;
existing valid schemas remain unchanged;
full compatibility/registry/plugin/Nix package gates stay green.

Tracks safe plugin-defined memory schemas under #7.

## Problem `MemorySchema.__post_init__()` assumes its descriptor fields already have the annotated runtime types. Malformed names/scopes/predicate collections can leak raw Python `TypeError` or create mutable/non-canonical schema descriptors instead of failing at the plugin's schema boundary. ## Required behavior - schema name must be non-empty text within the existing 128-character bound; - allowed scopes and fact predicates must be `frozenset[str]` values with non-empty text entries; - unsupported scopes still fail deterministically; - malformed descriptors raise `ValueError`, never incidental Python type errors; - existing valid schemas remain unchanged; - full compatibility/registry/plugin/Nix package gates stay green. Tracks safe plugin-defined memory schemas under #7.

nsaspy closed this issue

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