zara-memory: reject incomplete symbolic fact terms #132

New issue

Closed

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

nsaspy commented

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

Owner

Problem

The symbolic fact validator only anchors the predicate prefix (predicate(). Inputs such as workflow_state( therefore pass the predicate allowlist even though they are not complete predicate terms. That can admit malformed symbolic state at the plugin boundary.

Acceptance

deterministic RED proves incomplete/trailing-junk terms are currently accepted;
allowed simple predicate terms continue to work;
executable control syntax remains rejected;
validation stays parser-light and bounded rather than evaluating Prolog;
full compatibility/registry/plugin/package gates pass before merge.

Local integrity work under #7 only; this does not emulate symbolic-memory backend capabilities.

## Problem The symbolic fact validator only anchors the predicate prefix (`predicate(`). Inputs such as `workflow_state(` therefore pass the predicate allowlist even though they are not complete predicate terms. That can admit malformed symbolic state at the plugin boundary. ## Acceptance - deterministic RED proves incomplete/trailing-junk terms are currently accepted; - allowed simple predicate terms continue to work; - executable control syntax remains rejected; - validation stays parser-light and bounded rather than evaluating Prolog; - full compatibility/registry/plugin/package gates pass before merge. Local integrity work under #7 only; this does not emulate symbolic-memory backend capabilities.

nsaspy closed this issue

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