zara-coding: validate Prolog-RLM process policy descriptors #108

New issue

Closed

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

nsaspy commented

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

Owner

Problem

PrologRLMBridge.__init__() currently uses only timeout_seconds <= 0 and directly stores checkout/executable descriptors. Python booleans can therefore act as numeric timeouts, non-finite floats can bypass the positivity check, and malformed executable descriptors may survive until process execution.

Slice

deterministic RED coverage for boolean/non-finite/non-numeric timeout values and malformed executable descriptors;
fail during bridge construction before SWI-Prolog execution;
preserve Prolog-RLM command surface and checkout semantics;
exact-head compatibility, registry, plugin and Nix gates before merge.

Dependency-ready correctness/security slice within #1. No cross-plugin composition or Core authorization bypass.

## Problem `PrologRLMBridge.__init__()` currently uses only `timeout_seconds <= 0` and directly stores checkout/executable descriptors. Python booleans can therefore act as numeric timeouts, non-finite floats can bypass the positivity check, and malformed executable descriptors may survive until process execution. ## Slice - deterministic RED coverage for boolean/non-finite/non-numeric timeout values and malformed executable descriptors; - fail during bridge construction before SWI-Prolog execution; - preserve Prolog-RLM command surface and checkout semantics; - exact-head compatibility, registry, plugin and Nix gates before merge. Dependency-ready correctness/security slice within #1. No cross-plugin composition or Core authorization bypass.

nsaspy closed this issue

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