zara-coding: require passing verification evidence before task completion #172

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

Persistent symbolic task state currently gates completion on the existence of any evidence record. That means a task with only {status:"failed"} verification evidence can still transition to completed, which is a false-success path.

Slice

deterministic RED proving failed-only evidence cannot complete a task;
completion succeeds only when Prolog-owned state contains at least one bounded verification record with canonical passing status;
failed/rejected evidence remains retained and visible rather than discarded;
reject unsupported evidence status values at the closed protocol boundary if needed to keep completion semantics unambiguous;
real SWI-Prolog test must run in the canonical zara-coding Nix test derivation;
no model assertion, cross-plugin private import, or second runtime may manufacture success;
full compatibility/registry/Nix/package gates before merge.

Local #1 work only; Zara Core #400 remains the required seam for future authorization-preserving cross-plugin execution/composition.

## Problem Persistent symbolic task state currently gates completion on the existence of any evidence record. That means a task with only `{status:"failed"}` verification evidence can still transition to `completed`, which is a false-success path. ## Slice - deterministic RED proving failed-only evidence cannot complete a task; - completion succeeds only when Prolog-owned state contains at least one bounded verification record with canonical passing status; - failed/rejected evidence remains retained and visible rather than discarded; - reject unsupported evidence status values at the closed protocol boundary if needed to keep completion semantics unambiguous; - real SWI-Prolog test must run in the canonical zara-coding Nix test derivation; - no model assertion, cross-plugin private import, or second runtime may manufacture success; - full compatibility/registry/Nix/package gates before merge. Local #1 work only; Zara Core #400 remains the required seam for future authorization-preserving cross-plugin execution/composition.

nsaspy closed this issue

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