zara-coding: add persistent Prolog-owned symbolic task state #174

New issue

Closed

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

nsaspy commented

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

Owner

Problem

#1 requires Prolog-RLM to own symbolic coding task state and completion criteria, but zara-coding currently uses one-shot SWI-Prolog subprocesses for SPEC operations. There is no state surviving between tool calls, so task goals/dependencies/completion evidence cannot actually be Prolog-owned.

Vertical slice

Add a bounded persistent SWI-Prolog task-state session owned by the service plugin:

fixed trusted Prolog driver; JSON-line closed command protocol only;
no caller-supplied Prolog goals/eval/call surface;
create/read task state with bounded goal, constraints, dependencies and completion criteria;
record structured verification evidence;
completion fails closed until verification evidence exists;
one session persists across multiple task operations and is deterministically stopped with the plugin;
missing/unavailable Prolog-RLM degrades honestly rather than breaking plugin discovery/startup.

This is local #1 work. It does not implement cross-plugin PLAN/BUILD/EXECUTE composition, which remains blocked on Zara Core #400.

## Problem #1 requires Prolog-RLM to own symbolic coding task state and completion criteria, but `zara-coding` currently uses one-shot SWI-Prolog subprocesses for SPEC operations. There is no state surviving between tool calls, so task goals/dependencies/completion evidence cannot actually be Prolog-owned. ## Vertical slice Add a bounded persistent SWI-Prolog task-state session owned by the service plugin: - fixed trusted Prolog driver; JSON-line closed command protocol only; - no caller-supplied Prolog goals/eval/call surface; - create/read task state with bounded goal, constraints, dependencies and completion criteria; - record structured verification evidence; - completion fails closed until verification evidence exists; - one session persists across multiple task operations and is deterministically stopped with the plugin; - missing/unavailable Prolog-RLM degrades honestly rather than breaking plugin discovery/startup. This is local #1 work. It does not implement cross-plugin PLAN/BUILD/EXECUTE composition, which remains blocked on Zara Core #400.

nsaspy closed this issue

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